-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Can't install on node v0.11.13 and v0.11.14 OS X, but you can build it manually... #563
Comments
BTW this is the first time I'm experiencing libsass first-hand, and I can't believe how blitz fast it is!!! 👍 💯 !!! Great work. |
Hey @naartjie, thanks for the detailed issue report and the workaround steps. Those are good candidate of docs IMO. (PR is welcome) 👍 Currently, node-js is supported with stable node.js version, viz v0.10.33. The reason being, couple of (npm) dependencies have issue with nightly builds of node.js (or vice-versa?). Well that's way its not a stable build I suppose. :) As soon as they fix the issues, node-sass will brilliantly work with bleeding edge version of njs. |
Sure thing, it's done. Just didn't think I'd make it onto the front page news ;-) |
+1 Worked perfectly. After cloning I checked out the latest tag. Just to be safe... |
FYI this now appears to be an issue for io.js as well. |
FYI updating Basically I can PR a change to the
|
@snowstorm, lets not discuss this under a closed issue. We have #627 opened or you can start a separate thread.
We review each PR thoroughly. If the proposed solution work across the board (Node.js v0.10.35+, io.js v1.0.0+), I don't see why would anyone vote against it. |
Thanks @am11, I'll move my efforts over there. I'm glad to know if the PR is solid and supports v0.10, (v0.11?), io.js v1.0, it is likely to get merged :) |
Give maps a speed boost
----- It is inappropriate to include political and offensive content in public code repositories. Public code repositories should be neutral spaces for collaboration and community, free from personal or political views that could alienate or discriminate against others. Political content, especially that which targets or disparages minority groups, can be harmful and divisive. It can make people feel unwelcome and unsafe, and it can create a hostile work environment. Please refrain from adding such content to public code repositories.
I was trying to install node-sass using node
v0.11.13
andv0.11.14
today on OS X, with npmv2.1.11
. I couldn't get it to work, and I googled really hard for any solutions, but couldn't find any. I found a couple of bugs reported (eg #550 #490), and eventually info that only nodev0.10.x
is supported, so you should use that.I really wanted to get it working I kept trying and eventually got it to build manually. So I though I'd share the steps here in case someone wanted to get node-sass running on
v0.11.x
:Follow the rebuilding binaries steps from the readme:
Stop here, and comment this line out before continuing on with:
Then uncomment it again, and continue:
That's it, you should now have a working
./bin/node-sass
, which you cannpm link
to be globally available.The text was updated successfully, but these errors were encountered: