-
Notifications
You must be signed in to change notification settings - Fork 380
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
libsass bindings not found error on v1.3.1, v1.3.2 #174
Comments
It sounds like it's somehow pulling in the wrong version of libsass from somewhere. Is it possible you've installed node-sass globally at some point? |
I can confirm i don't have node-sass installed globally. |
I'm unable to reproduce this. Can anyone else? |
Same issue here. node-sass not install globally. (OSX 10.10; node installed via brew; latest npm) Error while installing: tunneling socket could not be established, cause=connect ECONNREFUSED But i think this error is related to node-sass not gulp-sass. |
Same error on v1.3.2 on Ubuntu. node-sass installed globally and local. And there's no errors when I run node-sass manually. |
@kelkes I ran into the same issue on osx, needed to clean my |
@kelkes : Let me know if @steffenmllr's solution works for you because I'm still not able to reproduce the error. |
@dlmanning @steffenmllr solution worked for me too. |
Then |
something wrong with binding in node-sass package inside gulp-sass. |
I'm seeing this same problem in 1.3.3. Error: None of the workarounds seemed to help. I don't have a |
have you actually performed I got the same problem again on another machine, but didn't need to add a |
@konclave solution fixed the issue for me. |
@konclave fix worked for me too. Nice one! |
I same issue and had good luck with |
@adam-beck I'm having the same problems as you with 1.3.3, did you already solve it? |
Had the same issue and running On the way there I also re-installed node-sass, not sure if this is also related. |
@arnellebalane I ended up having node-sass installed globally (if I remember correctly) but it was not in the usual place. I'd recommend blowing out your I'm sorry if this doesn't make much sense because I don't fully remember how I solved my problem. |
@joe-watkins Thanks! This fixed my issue! -Also of note I installed node-sass before this |
@joe-watkins, your solution is the only one that worked for me |
Can confirm, @joe-watkins has the working solution. |
The @konclave fix worked for me. Initially had node-sass installed at 2.0.1 with grunt-sass, uninstall and reinstalled to 2.1.1. |
Thanks @joe-watkins, #174 (comment) works! |
+1 for npm uninstall --save-dev grunt-sass or gulp-sass and then reinstall. |
+1 for @joe-watkins |
This did the job for me but I also had to run the same procedure for npm uninstall gulp-sass node-sass --save-dev
npm install gulp-sass node-sass --save-dev |
@joe-watkins worked. thx. :-) 👍 |
我试了各种办法。各种卸载各种重装。 finally it works for me . @joe-watkins thanks. |
Encountered this same issue, but running an automated build process with ansible and vagrant with an nfs file mapping to the host OS, so thought I would document my findings here and for #249 as The following command works, but breaks if you have two different OS's trying to access the same filesystem, as uninstall will remove the build for the other OS The solution is to add a postinstall step to your package.json and then make sure npm install is then run separately on both OS's after the uninstall / reinstall There was a second difficulty as npm rebuild wasn't picking up many of the nested dependencies for some reason, so I had to manually add them, one by one, to my project package.json. The rebuild step finally worked, but npm started throwing out many version conflict warnings, but deleting node_modules and doing a clean npm install got npm to map to the correct dependences again Final Solution:ansible - main.yml
package.json
command line:
|
Is this back? I just encountered this error with The solution (uninstall and reinstall |
But node-sass is a dependency of gulp-sass and it's node-sass that is trying to get libsass. |
From a node-sass issue on this topic (emphasis added): "This appears to be resolved. TLDR; if you've recently updated your version of node, or node-sass be sure to remove you node_modules dir because we use native extensions. In the future #1017 will prevent or warn about these types of issues." |
I have this problem when I run "ionict setup sass". It messes up the look of my project and after that command this is the log information that I get. Can anyone help? goldenchino@goldenchino-MacBook:~/example$ ionic setup sass
Can not download file from https://raw.githubusercontent.com/sass/node-sass-binaries/v2.1.1/linux-x64-node-4.0/binding.node
module.js:338 Error: Cannot find module '/home/goldenchino/example/node_modules/node-sass/node_modules/pangyp/bin/node-gyp'
module.js:338 Error: Cannot find module '/home/goldenchino/example/node_modules/node-sass/node_modules/pangyp/bin/node-gyp' Successful npm install Ionic project ready to use Sass!
/home/goldenchino/example/node_modules/node-sass/lib/index.js:22 Error: Error running gulp sass Exception with (CLI v1.6.4) Your system information: Cordova CLI: 5.2.0 |
It's depending on a old version of gulp-sass which links to an outdated version of node-sass (hence why it couldn't find the bindings). |
Keats, how would I re-install gulp-sass. |
just add/replace the gulp-sass version in the package.json, rm -rf node_modules and npm install |
I get the following after running the npm install command.
Can not download file from https://raw.githubusercontent.com/sass/node-sass-binaries/v2.1.1/linux-x64-node-4.0/binding.node
module.js:338 Error: Cannot find module '/home/goldenchino/example/node_modules/node-sass/node_modules/pangyp/bin/node-gyp'
module.js:338 Error: Cannot find module '/home/goldenchino/example/node_modules/node-sass/node_modules/pangyp/bin/node-gyp' npm WARN EPACKAGEJSON example@1.0.0 No repository field. |
I recently updraded to node 4.0 and got the exact same error as @MontesinosFernando also using ionic I tried following all the suggestions above. None of it works for me. |
Iconic uses an very old version of node-sass which is not compatible with You should open an issue with iconic to update to node-sass 3.3.3 since the
|
Thanks @konclave that worked out for me. First I removed the node-sass folder and then I run npm install node-sasscommand. |
The only thing that worked for me:
|
@joe-watkins thank u 🙏 |
I just had this issue and solved it by altering the dependancy of node-sass-middleware to the 3.3.2 version in package manager |
This is happening to me on CircleCI, but it works if I re-build after the first failure. Is there a way to permanent way to fix this? |
To be completely clear this issue happens because the version of node that npm used to install it's modules is different from the version you're trying to execute node-sass with. This can happen a couple different ways, the most common are:
Either the fix to rebuild node-sass
The long term solution is to figure why your node version is changing (if you're not doing it on purpose). Looking at the contents of the node-sass |
@joe-watkins Thank You, your solution worked great |
@joe-watkins - Thank you! finally worked with your solution! 👍 |
@ericsoco you saved my life. I had been trying all the other solutions for days but only yours work. |
@joe-watkins this is the only solution works for me! tks |
Thank you to everyone on this page who helped contribute to me finally resolving this issue... This FINALLY worked for me - after HOURS of struggle...
|
The user maketroli listed his method here which worked very well. I'd recommend doing a fresh install of the node modules first though.
|
I was prevoiusly running gulp-sass 1.2.4(node-sass 1.2.3 dep.) and everything was working perfectly. But I deleted my node_modules folder, and upon npm reinstallation, npm installed gulp-sass 1.3.1(node-sass 2.0.0-beta) as a result of "^1.2.4" in package.json. when i try to compile sass with this version I get the error: "
libsass
bindings not found. try reinstallingnode-sass
?"wordkaround: I simply rolled back to gulp-sass 1.2.4 and its working fine again.
The text was updated successfully, but these errors were encountered: