-
Notifications
You must be signed in to change notification settings - Fork 1.3k
node-sass 3.3.3 does not seem to work on Node 4 #1185
Comments
Same error here |
As one can see from the npm output you are getting node-sass 2.1.1, not 3.3.3. You need to update your project dependencies, since the newest gulp-sass uses the newest node-sass as well. |
Yep @saper you're correct: for anyone else that has this problem I had both 3.3.3 installed top level and 2.1.1 installed deeper in the same dependency tree. I cleaned out my tree and used npm v3 (which installs to the top level by default) to reduce the redundancy. Sorry for wasting your time! |
Could you elaborate more on how you "cleaned out your tree"? I seem to be having the same problem that you did, but I'm not sure what "cleaning out the tree" means. Thanks! |
Could you elaborate more on how you "cleaned out your tree"? I seem to be having the same problem that you did, but I'm not sure what "cleaning out the tree" means.
Most probably "rm -rf node_modules"
Did you try "npm rebuild node-sass" already?
|
Thanks, cleaning out node_modules and reinstalling everything fixed it for me. |
@Lothiraldan clean your dependencies as indicated above. |
Per #1122, I am using the latest node-sass on the current stable node release.
However building fails on pangyp:
node-sass then complains it is doesn't have a working binary:
The text was updated successfully, but these errors were encountered: