gulp-sass: Install fails - Windows 2008 - Error: `libsass` bindings not found. Try reinstalling `node-sass`?

Can someone give me a pointer here?

Trying to automate a build on a TeamCity server that’s running on Windows 2008. For some reason, all the other npm packages install. But gulp-sass install seems to keep failing:

> Error: `libsass` bindings not found. Try reinstalling `node-sass`?
>      at getBinding (G:\[...]\node_modules\gulp-sass\node_modules\node-sass\lib\index.js:21:11)
>      at Object.<anonymous> (G:\[...]\node_modules\gulp-sass\node_modules\node-sass\lib\index.js:211:23)
>      at Module._compile (module.js:456:26)
>      at Object.Module._extensions..js (module.js:474:10)
>      at Module.load (module.js:356:32)
>      at Function.Module._load (module.js:312:12)
>      at Module.require (module.js:364:17)
>      at require (module.js:380:17)
>      at Object.<anonymous> (G:\[...]\node_modules\gulp-sass\index.js:3:17)
>      at Module._compile (module.js:456:26)
>      at Object.Module._extensions..js (module.js:474:10)

If I track the error to earlier in the log, this is what I find:

> fs: missing callback Error: EPERM, unlink 'G:\[...]\node_modules\gulp-sass\node_modules\node-sass\vendor\win32-ia32\binding.node'

Happens every time. I tried installing node-sass directly too, which seems to pass without errors, but gulp-sass still throws the EPERM and libsass error anyway.

Thoughts?

About this issue

Original URL
State: closed
Created 9 years ago
Comments: 23 (1 by maintainers)

Commits related to this issue

moved sass-material-colors into node_module, where it should be. Also patched a gulp-sass error that showed up after I updated node. https://github.com/dlmanning/gulp-sass/issues/185#issuecomment-7209... — committed to Laidlaw/alanlaidlaw-ancient by Laidlaw 9 years ago

Most upvoted comments

Try this fixes:

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

+17

ghost on Mar 13, 2016

@For me this sudo npm install -S gulp-sass@latest fixed the problem. I have centos6.5, node v4.4.7 and npm 3.10.4

+13

sumanbogati on Jul 8, 2016

Reinstalling gulp-sass fixed it for me, thanks @mpiasta-ca

benmirkhah on Jun 9, 2015

I am still having trouble with this. I’ve tried several things:

Uninstalled gulp-sass and node-sass
Installed node-sass and then gulp-sass in that order
Ran ‘npm rebuild node-sass’ as the error suggested but the “Binary is fine.”
Uninstalled node.js x64 and installed node.js x86

When I require sass = (‘gulp-sass’); in gulpfile.js Visual Studio throws the error. When I comment that line Visual Studio doesn’t throw the error but obviously I can’t run any tasks that use gulp-sass. I don’t seem to be having the same issue when running the same tasks using Node.js CMD.

I am on Windows 10 x64 and using Visual Studio 2015 Professional. Node version 4.2.2, NPM version 2.14.7. After reading a lot of posts, it seems like this is a binding issue as it’s looking for a folder called win32-ia32-11 when I have a folder called win32-ia32-46? Any help would be greatly appreciated.

haydenhancock on Nov 4, 2015

Found a temporary solution. When I first run npm install node-sass@1.0.3 before installing gulp-sass, it seems to work after that.

https://github.com/sass/node-sass/issues/497#issuecomment-61116327

mpiasta-ca on Jan 29, 2015