-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install fails - Windows 2008 - Error: libsass
bindings not found. Try reinstalling node-sass
?
#185
Comments
Found a temporary solution. When I first run |
See #174 |
Reinstalling gulp-sass fixed it for me, thanks @mpiasta-ca |
@mpiasta-ca Your solution works for me, thanks! |
… patched a gulp-sass error that showed up after I updated node. dlmanning/gulp-sass#185 (comment)
For me the solution was like this: It turned out, that I had a version of "node-sass" in my node-modules path. You can find it with this statement:
After removing this node-sass module completely, I was able to reinstall gulp-sass and then it worked perfectly. |
This worked for me, I had to first install node-sass with sudo (I'm on Mac), and then subsequently install gulp-sass |
|
thanks @benmirkhah 👍! |
I am still having trouble with this. I've tried several things:
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. |
I resolved by issue with Visual Studio by moving the PATH variable higher in priority as found here. |
If you still get this issue upgrade to gulp-sass 2.1. |
Try this fixes: sudo npm install -g n |
@indahibrahim This doesn't work in VS, because VS still runs as 32 bit... n is 64 bit. |
@haydenhancock Make sure you're not using a beta version of gulp-sass |
It's worked for me |
@for me this |
Yeah installing latest gulp-sass works also, or remove your node-modules and npm i |
@sumanbogati Thanks for the solution provided, it solved my problem too after failing to fix it using the commands like |
I was facing this issue. In my case the parent package.json was referring to new version of node-sass but the version of gulp-sass was referring to old node-sass. As soon as I updated gulp-sass to latest version, and ran 'npm rebuild node-sass', issue was gone. |
My package.json had older version of gulp-sass, updated it to "gulp-sass": "^2.3.2" and did npm install. It worked ! |
I had a older version and running npm install -D gulp-sass@latest fix the problem |
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:If I track the error to earlier in the log, this is what I find:
Happens every time. I tried installing
node-sass
directly too, which seems to pass without errors, butgulp-sass
still throws the EPERM and libsass error anyway.Thoughts?
The text was updated successfully, but these errors were encountered: