npm install throwing error in node-sass

Question

node-sass@2.1.1 install /home/user/Documents/project/node_modules/node-sass
> node scripts/install.js

WARN invalid config loglevel="notice"
Can not download file from https://raw.githubusercontent.com/sass/node-sass-binaries/v2.1.1/linux-x64-node-8.2/binding.node

> node-sass@2.1.1 postinstall /home/user/Documents/project/node_modules/node-sass
> node scripts/build.js

module.js:487
    throw err;
    ^

Error: Cannot find module '/home/user/Documents/project/node_modules/node-sass/node_modules/pangyp/bin/node-gyp'
    at Function.Module._resolveFilename (module.js:485:15)
    at Function.Module._load (module.js:437:25)
    at Function.Module.runMain (module.js:605:10)
    at startup (bootstrap_node.js:158:16)
    at bootstrap_node.js:575:3
Build failed
added 2186 packages in 42.166s

I tried so far:

npm rebuild

npm rebuild node-sass

npm uninstall -g node-sass

rm -rf node_module

It seems you need to have `node-gyp` installed. `npm install -g node-gyp` — Mekicha, Aug 09 '17 at 11:22
`node-sass@2.1.1` is severely outdated (I tried installing it and was able to reproduce the error); you can try editing `package.json` to use the most recent version instead. (remove `@2.1.1)` — , Aug 09 '17 at 11:25
TLDR: replace node-sass with sass. Also not to be "that guy" but there are a lot of wildly incorrect or just strange answers here. Don't bother with python or ruby or node-gyp, just replace it with the pure JS sass - it's identical but takes about 1% of the time to install and won't cause headaches in different envs. — Matt Fletcher, Feb 08 '23 at 11:06

Usama Muhammad · Answer 1 · 2023-04-05T15:35:22.047

22

Remove 'node-sass' dependency from your package.json
run npm install
run npm i sass
run npm start

You're ready to go! :)

edited Apr 05 '23 at 15:35

answered Feb 12 '22 at 21:35

Usama Muhammad

321
2
4

Thanks alot. Saved me days of headaches – Haikal Nashuha Nov 17 '22 at 01:37
I LOVE YOU!!!! Thank you! Moving from node-sass to sass did it for me! After half a day of trying the deprecate-Node-version route and upgrade-node-sass-version route... Thank you so much! – Lazar Dec 26 '22 at 10:41
Wonderful! I'm old-school and didn't know there was a pure JS implementation of sass. – Matt Fletcher Feb 08 '23 at 10:55
Edited your answer Usama, hope that's okay. – Matt Fletcher Feb 08 '23 at 11:03

score 12 · Answer 2 · answered Oct 04 '18 at 23:07

12

You need to do next steps and it should work:

rm -rf node_modules package-lock.json 
npm install --saveDev node-sass@4.5.3 
npm install

Voila :)

answered Oct 04 '18 at 23:07

olllejik

1,404
1
10
13

1

what is the significance of specific version 4.5.3? How to determine this version for my environment? My package.json is tryign to install ^4.11.0 node-sass – dejjub-AIS Dec 01 '19 at 13:25

score 4 · Answer 3 · edited Apr 02 '20 at 04:40

4

by using yarn run:

yarn add node-sass

edited Apr 02 '20 at 04:40

Buddy

10,874
5
41
58

answered Apr 02 '20 at 04:39

iaMartisan

49
2

score 4 · Answer 4 · answered Sep 28 '20 at 14:03

4

node-sass has minimum dependency according to the version of node installed in your system. You can find out the minimum version required here

answered Sep 28 '20 at 14:03

Kirtan Desai

91
7

score 4 · Answer 5 · answered Oct 22 '20 at 12:06

4

Removed package-lock.json, installed Python 2.7, added an env variable for python path. Ran npm install. Voila !

answered Oct 22 '20 at 12:06

Sagar Khatri

575
3
16

score 3 · Answer 6 · answered Mar 21 '21 at 17:29

3

Use

Node : v14.16.0
node-sass: ^4.14.1

it works for me

answered Mar 21 '21 at 17:29

Awadhesh Kumar

39
1

score 3 · Answer 7 · edited Jul 26 '22 at 11:09

3

This question is old, but if you arrive here in 2022 or later, then this info may be useful:

node-sass is deprecated. Now you should use sass.

That's why the answer given by Usama Muhammad works. Hope this helps.

Sources:

edited Jul 26 '22 at 11:09

Tyler2P

2,324
26
22
31

answered Jul 25 '22 at 14:43

damandak

41
5

score 2 · Answer 8 · answered May 20 '22 at 14:10

2

Delete package-lock.json
Remove 'node-sass' dependency from your package.json
run npm install
run npm gulp-sass --save-dev
run npm i -d sass
run npm start

answered May 20 '22 at 14:10

saikumar yerra - sky

117
2

score 1 · Answer 9 · answered Aug 10 '17 at 00:44

1

The minimum version with Node 8 support is 4.5.3. Offhand, I don't think 2.x will support anything above Node 0.12, which is EOL.

answered Aug 10 '17 at 00:44

nschonni

4,069
1
28
37

score 0 · Answer 10 · answered Jan 25 '20 at 12:13

I have found I get node-sass errors when trying to install over a corporate proxy. The first solution is to ensure your .npmrc file has proxy allowance.

.npmrc

# Try removing reference to registry, as sometimes your local corporate registry of node_modules may not include node-sass
# // registry=https://....

# note if using special characters in pass, encode them: eg: h@ppy = h%40ppy
strict-ssl=false
proxy=http://<username>:<pass>@proxyhost:<port>
https-proxy=http://<uname>:<pass>@proxyhost:<port>

NODE_TLS_REJECT_UNAUTHORIZED = 0

Then in command line before running any install

set NODE_TLS_REJECT_UNAUTHORIZED = 0

Zip node-binding files from node-sass github site in order to download them over corporate network.

Example: https://github.com/inspiraller/node-sass-bindings

score 0 · Answer 11 · answered Mar 01 '20 at 17:12

0

Add manually in package.json : "node-sass": "4.13.0"

and update package.json in terminal npm install

answered Mar 01 '20 at 17:12

Anis GH

11

npm install throwing error in node-sass

11 Answers11

.npmrc

NODE_TLS_REJECT_UNAUTHORIZED = 0

Zip node-binding files from node-sass github site in order to download them over corporate network.

Linked