-
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
Module._extensions error with Node 0.12 #189
Comments
I'm using 64-bit node v0.12 on mac osx 10.10.2. Same error as above. module.js:355 |
Same here after upgrading nodejs to 0.12 |
Same here. |
For the record the problem here is with node-sass. It's not something I can fix. Follow this thread: sass/node-sass#653 |
Any estimate on when this will become compatible with 0.12? |
@kylescousin : Please read my comment above |
I used the current node-sass master and built the binaries myself. That worked fine. stream.js:94
throw er; // Unhandled stream error in pipe.
^
Error: invalid top-level expression I think this is an error of gulp-sass but I am happy to be corrected. |
@dlmanning fyi looks like they updated node-sass to the next version which resolves the issue. |
Yeah... Apparently node-sass has been updated to work in Node 0.12. But still gulp-sass is still not working. I'm looking forward to using gulp-sass. I'm new to Node dev workflows... So new that Node 0.12 is the first version I installed. And the first thing I wanted to do was compile some SASS using Gulp. Took me ages to work out it wasn't my technical ability that was messing things up. |
the newly released node-sass 2.0.0 still isn't building on iojs or node 0.12 for me. I've commented on the issue thread in the node-sass repo. I'll update the dependency when the build works (hopefully tomorrow). If anyone wants to try and see if they have more luck, just change the node-sass dependency to "^2.0.0" in package.json and |
Didn't work for me
|
Well I just updated to node-sass 2.0.1. The self-register error has gone... but now I have the following error
Is this because of me or is it something else that needs fixing? |
Fixed in 314ce5c |
Thanks @dlmanning |
it works!! you're amazing @dlmanning My old error: after using 1.3.3 it all works. |
@wdinau Thanks, but all the credit here goes to the node-sass team. |
I just updated to Node 0.12 on Windows 7 64 bit and am now receiving the following error. I uninstalled and reinstalled gulp-sass with no luck.
The text was updated successfully, but these errors were encountered: