Node-sass: Instalation stuck at node scripts/install.js [OS X]
When running npm install node-sass, the process is getting stuck at node scripts/install.js
I'm running: OS X 10.10.1
Node versions tested: v0.10.35, v0.11.14
jakub-c
All 16 comments
I am having the same issue, also running OS X 10.10.1 and node v0.10.35
interestinall
on 27 Jan 2015
Also experiencing issues with v0.11.14.
michaelBenin
on 27 Jan 2015
Same issue here
dzannotti
on 28 Jan 2015
Ok after a bit of head bashing i figured out that with node 0.10.36 everything works fine, so it's a compatibility problem with the latest node release, using nvm i was able to achieve what i needed
dzannotti
on 28 Jan 2015
I was just wondering... But I guess you are already working on a fix? Not sure how to start my first project now :)
On Win8.1 with node 0.10.36 ...?
christianromeni
on 29 Jan 2015
@christianromeni I'm not sure if you are sarcastic or you actually mean that you don't know how to start your project. If the latter is the case than you can install one of the previous versions by executing: npm install <package>@<version>, I suspect that something earlier than version 2 should work for you
jakub-c
on 29 Jan 2015
@christianromeni https://github.com/gruntjs/grunt-contrib-sass will work for you now. It is ruby based so you have to have that installed. Just look at the readme. I have heard it compiles a little slower than node-sass, but it probably won't be a big deal unless your project is huge.
interestinall
on 29 Jan 2015
Sorry, that was not beeing sarcastic.. I'm new to this...
I was trying not to use the grunt-contrib-sass because I didnt want to install ruby...
I'm currently installing by adding this line to my package.js: "grunt-bower-concat": "^0.4.0"
Could I just use a lower version (like 0.3.9??) and it will work?
christianromeni
on 29 Jan 2015
@christianromeni I just looked at grunt-bower-concat dependencies and it doesn't look like it has anything to do with node-sass, so if you've got a problem using grunt-bower-concat than I would recommend filing an issue on their repo page. However if it's still a node-sass issue you should do as you described, but instead of changing version of grunt-bower-concat in your package.json you should find node-sass and set an earlier version number to something preceding version 2, than remove your node_modules folder and reinstall everything with npm install
jakub-c
on 29 Jan 2015
Is it like the process stuck forever or it throws after sometime with an error message?
am11
on 29 Jan 2015
@am11 In my case it looks like it's stuck forever. I gave it a minute or two to compute but after no result I've just terminated the process, I believe it's enough time.
jakub-c
on 29 Jan 2015
I believe it's enough time.
Well I waited for ~30 mins, when I first encountered this error on Win. Eventually installation went through successfully. We figured out where it was hanging and fixed it. Now testing binary step (where it was hanging) was temporarily disabled in version v2.0.0-beta. Now it is really hard to guess what might be going wrong without any verbose output.
If you don't have time for such kind of diagnostic, then wait for vNext. We have some fixes in that area as well.
Momentarily, does this help? (manually binary installation)
am11
on 30 Jan 2015
@am11 Finally I had a while to test a solution suggested by you and it does work indeed. Thanks.
jakub-c
on 10 Feb 2015
@jakub-c, v2.0.1 (shortly after v2.0.0 stable) is released. Note that the current stable/production-ready version of node.js is v0.12. With node-sass v2+, we support both v0.10 and v0.12.
See node-sass release notes: https://github.com/sass/node-sass/releases/tag/v2.0.0
and that of node-sass-binaries: https://github.com/sass/node-sass-binaries/releases/tag/v2.0.0
am11
on 12 Feb 2015
@Centaur you problem is likely unrelated. Please open a new issue with the output from our troubleshooting guide
xzyfer
on 21 Jul 2015
I too thought there was a problem... After an hour: Ctrl + C
npm config set loglevel silly
npm install
.... It took 2 hours. But it finished. I'm using a shitty laptop and running from a USB root drive. This is on Ubuntu 14.04, inside docker. Worst case, you might want to check your filesystem or disk. Or upgrade your hardware.
dagelf
on 20 Mar 2016
Related issues
pulkitnandan
路
4Comments
harukaeru
路
3Comments
samayo
路
3Comments
alexandrubau
路
3Comments
nagyfej
路
3Comments
Most helpful comment
I too thought there was a problem... After an hour: Ctrl + C
npm config set loglevel silly
npm install
.... It took 2 hours. But it finished. I'm using a shitty laptop and running from a USB root drive. This is on Ubuntu 14.04, inside docker. Worst case, you might want to check your filesystem or disk. Or upgrade your hardware.