Try reinstalling `node-sass` on node 0.12?

Question

I would like to use google web starter kit. I installed node.js v0.12.0, node-sass & gulp.

And then ran:

$ sudo npm install

When I typed gulp serve then got this error:

Using gulpfile ~/web-starter-kit/gulpfile.js Starting 'styles'... 'styles' errored after 93 ms 
Error: `libsass` bindings not found. Try reinstalling `node-sass`? at getBinding

I reinstalled node and gulp but this doesn't help.

What should I do next?

Downgrading node worked for me. – zero_cool Jan 18 '17 at 22:48 — zero_cool, Jan 18 '17 at 22:48

score 386 · Answer 1 · answered Sep 19 '15 at 08:54

386

If your node version is 4 and you are using gulp-sass, then try

npm uninstall --save-dev gulp-sass

npm install --save-dev gulp-sass@2

answered Sep 19 '15 at 08:54

Roma Rush

4,148
1
14
15

5

fixed problem form me on node 4.1 :) ty – Zalaboza Sep 28 '15 at 00:30
Fixed for me on Debian 8.1 and Node 4.1 too. Thanks a lot. – VinceOPS Sep 28 '15 at 20:50
npm install --save-dev gulp-sass@3 did the job for me! :P – Alx Oct 02 '15 at 22:14
3

Thank you. Probably this answer should be marked as the "right one") – Paul Paca-Vaca Seleznev Oct 09 '15 at 10:28
1

Thank you, spent a lot of time trying to resolve this and this was the solution that worked! – HjalmarCarlson Nov 16 '15 at 19:26
This is the only solution working on node 4.2.3. Thanks! – Fred K Dec 18 '15 at 10:56
Using Win 8 and node 4+. This is the only solution that works, tried them all, literaly – Stephan Grobler Jan 14 '16 at 19:37
Yep this worked for me. Tried the other fixes such as rebuilding sass and none of them worked. I guess they're all related to different version of sass and node! – Brad Bird Feb 01 '16 at 21:17
Thank you so much! Mac, node v4.2.6 – tayvano Feb 18 '16 at 20:27
Thanks man! Just came across this issue and this fixed it for me :) – pourmesomecode Feb 25 '16 at 14:21
Thanks. Nice solution for Mac and node 5.8. – mikowiec Apr 03 '16 at 18:55
After running these commands, I had to run 'npm rebuild node-sass' then I was back in biz! – ed_is_my_name Aug 23 '16 at 14:59
Note that you may have to run the sudo command in front of it for permission issues ;-) – Mr Washington Oct 25 '16 at 05:51
1

Also solves the issue on v6.9.2 as of December 2016. Thanks! – digitalformula Dec 29 '16 at 10:59

Denis C de Azevedo · Answer 2 · 2015-06-14T14:05:36.630

340

I found this useful command:

npm rebuild node-sass

From the rebuild documentation:

This is useful when you install a new version of node (or switch node versions), and must recompile all your C++ addons with the new node.js binary.

http://laravel.io/forum/10-29-2014-laravel-elixir-sass-error

edited Jun 14 '15 at 14:05

answered May 06 '15 at 04:13

Denis C de Azevedo

5,971
2
28
46

5

Got a lot of errors, like `Python not supported by` and `Failed at the node-sass@0.8.6 install script 'node build.js'` – AlikElzin-kilaka Jun 10 '15 at 07:08
14

This should be the accepted answer, because it does minimum work to fix the actual problem. – TheHippo Jul 28 '15 at 19:02
1

@AlikElzin-kilaka: Make sure that you have Python installed and the _PYTHON_ environment variable set to point the installation. – Roope Hakulinen Aug 30 '15 at 09:00
2

I tried this before anything else and it worked perfectly. Cheers – ConorLuddy Sep 10 '15 at 09:54
15

I receive a ```Error: Cannot find module 'node_modules/node-sass/node_modules/pangyp/bin/node-gyp'``` – lrkwz Nov 04 '15 at 15:18
1

Worked perfectly for me. – B R Jan 04 '16 at 15:03

score 233 · Answer 3 · answered Mar 10 '15 at 21:40

233

I ran into this error using node 0.12.0 and it was fixed by deleting the existing /node_modules directory and running npm update.

answered Mar 10 '15 at 21:40

createbang

2,433
1
11
13

That won't work if you don't have all you dependencies specified in package.json – Victor Marchuk Apr 25 '15 at 13:15
I had to delete the folder, then run npm install, then npm update. But this pointed me in the right direction. Thanks! – Timothy Apr 28 '15 at 16:43
Deleting the node_modules folder caused: `Error: Cannot find module 'c:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'` when running `npm update`. – AlikElzin-kilaka May 04 '15 at 03:36
Worked great. Thanks! – Neil Monroe Jun 06 '15 at 01:02
41

This is the drastic solution. Just use `npm rebuild node-sass` which is specifically for rebuilding the C++ addons. – Chris Sattinger Jun 14 '15 at 12:43
I believe we ran into this problem with an internal project because of a node_modules directory that was accidentally committed along with the source into source control. – jpierson Jul 13 '15 at 12:59
Just running `npm update` worked for me. No need to delete anything. – Chuck Le Butt Jul 20 '15 at 15:39
2

Doesn't fix anything for me :( – Isochronous Jul 28 '15 at 20:12
It's a drastic solution but most people don't update their dependencies that often anyway - so this is a good practice to refresh where your project is at. – serraosays Nov 25 '15 at 12:52

Pupper · Answer 4 · 2015-10-16T00:16:57.957

84

npm rebuild node-sass was giving me errors (Ubuntu) and npm install gulp-sass didn't make the error go away.

Saw a solution on GitHub which worked for me:

npm uninstall --save-dev gulp-sass

npm install --save-dev gulp-sass

edited Oct 16 '15 at 00:16

answered Sep 15 '15 at 18:25

Pupper

2,225
2
20
28

Worked Today for @lastest versions – gtamborero Mar 13 '17 at 22:13

mikemaccana · Answer 5 · 2015-04-21T10:31:01.107

22

I had the same issue:

installing node-sass
being told at the end of installation that the installation completed successfully
then being asked to re-install node-sass.

The solution is to install node-sass version 2 which supports current versions of node. See https://github.com/sass/node-sass/issues/490#issuecomment-70388754

Run:

npm install node-sass@2

Then re-test:

$ npm ls node-sass
myapp@0.0.0 /var/www/myapp
└── node-sass@2.0.1

$ gulp sass
[09:48:42] Using gulpfile /var/www/myapp/gulpfile.js
[09:48:42] Starting 'sass'...
[09:48:42] Finished 'sass' after 15 ms

edited Apr 21 '15 at 10:31

answered Mar 19 '15 at 22:33

mikemaccana

81,787
73
317
396

8

For those of us using 'grunt-sass' be sure and update: 'npm install --save-dev grunt-sass' – natepers Apr 08 '15 at 19:55

score 19 · Answer 6 · answered May 06 '15 at 14:16

19

If you use Gulp then try:

npm install gulp-sass

I had the same problem and the gulp-sass package was the problem.

answered May 06 '15 at 14:16

georger

1,310
19
23

using this one after "npm uninstall --save-dev gulp-sass" fixed the problem for me – Sul Aga Aug 02 '15 at 13:17
2

`npm install grunt-sass` fixed the problem for me. – Paul Schreiber Sep 17 '15 at 16:57

score 11 · Answer 7 · answered Oct 29 '16 at 06:01

11

i had the same problem today at work.

npm rebuild node-sass

done the job for me

answered Oct 29 '16 at 06:01

bin2hex

307
2
13

natepers · Answer 8 · 2015-02-26T23:11:01.030

9

Downgrading Node to 0.10.36 should do it per this thread on the node-sass github page: https://github.com/sass/node-sass/issues/490#issuecomment-70388754

If you have NVM you can just:

nvm install 0.10

If you don't, you can find NVM and instructions here: https://www.npmjs.com/package/nvm

edited Feb 26 '15 at 23:11

answered Feb 25 '15 at 16:26

natepers

524
4
12

solved the issue for me. nvm is also available via homebrew for mac users: "brew install nvm". after switching to the 0.10.36 version, make sure it is really active: "node -v" – cjoy Mar 11 '15 at 18:43
9

Downgrading node itself is more of a workaround than an answer. – mikemaccana Mar 24 '15 at 10:05
1

This bug is fixed in node-sass@2.0.1- as @mikemaccana discovered at the end of the ticket referenced by this answer. See his comment in this thread. – natepers Apr 06 '15 at 20:41
1

'grunt-sass' users should update after updating 'node-sass' if you're still experiencing trouble: 'npm install --save-dev grunt-sass' – natepers Apr 08 '15 at 19:57

score 3 · Answer 9 · answered Sep 09 '15 at 23:19

This answer is a bit orthogonal to the the OP, but --

libsass bindings don't install properly with the node-sass wrapper on Node v4.0.0. I got the same error message as in the question (Error: 'libsass' bindings not found. Try reinstalling 'node-sass') but I ended up uninstalling Node v4.0.0 and installing v0.12.7 using nvm, via this script:

https://gist.github.com/brock/5b1b70590e1171c4ab54

and now libsass and node-sass are behaving properly.

score 2 · Answer 10 · answered May 01 '15 at 18:52

2

you may also want to npm remove gulp-sass and re-install gulp-sass if you've switched node versions.

answered May 01 '15 at 18:52

4m1r

10,632
8
40
51

score 2 · Answer 11 · answered Nov 12 '15 at 16:05

2

I have same issue when gulp-sass version is 1.3.0, and fix it after upgrading to 2.1.0.

answered Nov 12 '15 at 16:05

Kos

61
6

score 1 · Answer 12 · answered Jan 19 '16 at 18:10

If you came here because you upgraded nodejs systemwide & suddenly your emberjs ^1.13 app is failing with this message, make sure you're not using an outdated version of ember-cli-sass. You'll need to rm -rf node_modules bower_components dist tmp within the Ember app, then update your package.json with the appropriate ember-cli-sass version, and finally npm install --save-dev. This fixed it for me, without having to rebuild or change any other dependencies.

Florin Dobre · Answer 13 · 2016-06-17T19:49:53.977

1

I removed all the /node_modules folder then ran npm install and it worked.

I have node v5.5.0, npm 3.3.12

edited Jun 17 '16 at 19:49

answered Mar 23 '16 at 14:25

Florin Dobre

8,025
2
45
68

score 0 · Answer 14 · answered Aug 04 '15 at 18:10

For me, this issue was caused in my build system (Travis CI) by doing something kind of dumb in my .travis.yml file. In effect, I was calling npm install before nvm use 0.12, and this was causing node-sass to be built for 0.10 instead of 0.12. My solution was simply moving nvm use out of the .travis.yml file’s before_script section to before the npm install command, which was in the before_install section.

In your case, it is likely that whatever process you are starting with gulp is using a different version of node (than what you would expect).

score 0 · Answer 15 · answered Nov 16 '15 at 20:03

0

I had the same issue as @Kos had, only for some reason I had to modify the gulp-sass package from the old package.json file I had. It then installed the dependencies currently and now it finally works!

answered Nov 16 '15 at 20:03

Shay

1,812
2
14
22

score 0 · Answer 16 · answered Mar 16 '16 at 14:28

0

My issue was that I was on a machine with node version 0.12.2, but that had an old 1.x.x version of npm. Be sure to update your version of npm: sudo npm install -g npm Once that is done, remove any existing node-sass and reinstall it via npm.

answered Mar 16 '16 at 14:28

k00k

15,534
13
54
82

score 0 · Answer 17 · answered Nov 08 '16 at 19:00

0

You need to use the right version. Try:

nvm use 0.12

answered Nov 08 '16 at 19:00

alexfigtree

1,238
12
16

Try reinstalling `node-sass` on node 0.12?

17 Answers17

Linked