libsass bindings not found when using node-sass in nodejs

node.js Problem Overview

I want to use the node-sass module in my node.js v0.12 application to benefit from the performance of libsass.
I executed npm i node-sass to install the module, no errors so far.

Now the mess starts:
If I just open the REPL in a terminal to try out node-sass then everything works fine but if I include it in my project files and run node myfile.js then I get the following error message:

Error: `libsass` bindings not found. Try reinstalling `node-sass`?

The module's description at npmjs.com states that there might be a problem with resolving #!/usr/bin/env node under Ubuntu and how to fix this but that is not the case on my machine.
I could not find anything useful so I hope that you might help me.

I'm using node v0.12.2 under Ubuntu 14.10.

P.S.: I already tried to reinstall node-sass but without success. Nothing changes.

node.js Solutions

Solution 1 - node.js

If you're using node 4.x or later then you need to reinstall gulp-sass with:

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

Solution 2 - node.js

You’ve probably tried to reinstall node-sass while using

npm install node-sass

npm uninstall node-sass
npm install node-sass

But node-sass is a C version of Sass. You have to use npm rebuild:

npm rebuild node-sass

Solution 3 - node.js

I fixed this issue by deleting the existing /node_modules folder and running npm update

Solution 4 - node.js

This is the only solution that worked for me,

sudo npm install -g n
sudo n 0.12.7
npm install node-sass@2
sudo npm -g install node-gyp@3
npm rebuild node-sass

Solution 5 - node.js

This workaround (http://forum.ionicframework.com/t/error-running-gulp-sass/32311/20) worked form me.

Starting with this setup:

Cordova CLI: 5.3.3 Gulp version: CLI version 3.9.0 Gulp local: Local version 3.9.0 Ionic Version: 1.1.0 Ionic CLI Version: 1.6.5 Ionic App Lib Version: 0.3.9 ios-deploy version: Not installed ios-sim version: 5.0.1 OS: Mac OS X Yosemite Node Version: v4.1.1 Xcode version: Xcode 6.4 Build version 6E35b

I've found a solution to avoid to use 'sudo' command. We need before to fix npm permissions following this: https://docs.npmjs.com/getting-started/fixing-npm-permissions and fixing permissions for Node here: http://mawaha.com/permission-fix-node-js/ After this we can check and reinstall software without 'sudo' for npm, n or ionic.

I followed this step:

npm install -g n
rm -R node_modules/ 
npm install node-sass@3.3.3 
npm -g install node-gyp@3
npm uninstall gulp-sass
npm install gulp-sass@2 
npm rebuild node-sass 
ionic setup sass

Why [email protected]? Because it works with latest ionic version: https://github.com/driftyco/ionic/pull/4449

Solution 6 - node.js

Combining the two answers above worked for me, plus additions:

sudo npm uninstall --save gulp-sass
npm install --save gulp-sass@2
npm update
npm rebuild node-sass

Solution 7 - node.js

I have solved this to create the right directory with the specified binding.node file. You can download the bindings from github

https://github.com/sass/node-sass-binaries

Look in the error message the path where it tries to find the binding. In my case:

C:\Users\Martijn\Documents\node_modules\gulp-sass\node_modules\node-sass\vendor\win32-x64-46

So I create this map win32-x64-46 and copy the binding from github in.

Solution 8 - node.js

My solution was to downgrade to v0.10.25 (try sudo n 0.10.25 if you use n)

Solution 9 - node.js

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.

Solution 10 - node.js

This was a Node version issue for me, try using nvm to backtrack your version to something like: 0.10.32. This worked for me. I was running 4.2.2

Solution 11 - node.js

I solved this problem by updating my gcc from 4.4.x to 4.7.x

Solution 12 - node.js

No need for sudo or re-installations. This has always worked for me:

nvm use 0.12.2

Solution 13 - node.js

This is the steps I undertook to fix my issue.

I updated my node manually to the latest version
Reinstalled node-sass

npm install node-sass

3.npm audit fix to fix certain vulnerabilities.

`npm audit fix`

5.npm install node-sass

 `npm install node-sass`

worked and compiled properly thereafter. I apologize if anything related to my answer isn't right. I'm just a beginner. Hope it works for you

Content Type	Original Author	Original Content on Stackoverflow
Question	TorbenJ	View Question on Stackoverflow
Solution 1 - node.js	Wilson Silva	View Answer on Stackoverflow
Solution 2 - node.js	Philipp Andreychev	View Answer on Stackoverflow
Solution 3 - node.js	Dallas Clark	View Answer on Stackoverflow
Solution 4 - node.js	Stranger	View Answer on Stackoverflow
Solution 5 - node.js	Francesco	View Answer on Stackoverflow
Solution 6 - node.js	Jadeye	View Answer on Stackoverflow
Solution 7 - node.js	MartijnBrands	View Answer on Stackoverflow
Solution 8 - node.js	nathanhleung	View Answer on Stackoverflow
Solution 9 - node.js	Alan H.	View Answer on Stackoverflow
Solution 10 - node.js	Kevin Alwell	View Answer on Stackoverflow
Solution 11 - node.js	worldask	View Answer on Stackoverflow
Solution 12 - node.js	alexfigtree	View Answer on Stackoverflow
Solution 13 - node.js	Pierce D'souza	View Answer on Stackoverflow