Skip to content
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

Closed
rcollette opened this issue Feb 8, 2015 · 17 comments
Closed

Module._extensions error with Node 0.12 #189

rcollette opened this issue Feb 8, 2015 · 17 comments

Comments

@rcollette
Copy link

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.

Failed to load "C:\code\rcollette\RequestAngularTS\RequestAngularTS.Web\gulpfile.js"...
module.js:355
  Module._extensions[extension](this, filename);
                               ^
Error: The specified procedure could not be found.

C:\code\rcollette\RequestAngularTS\RequestAngularTS.Web\node_modules\gulp-sass\node_modules\node-sass\vendor\win32-x64\binding.node
    at Error (native)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (C:\code\rcollette\RequestAngularTS\RequestAngularTS.Web\node_modules\gulp-sass\node_modules\node-sass\lib\index.js:211:15)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
@chyld
Copy link

chyld commented Feb 8, 2015

I'm using 64-bit node v0.12 on mac osx 10.10.2. Same error as above.

module.js:355
Module._extensions extension (this, filename);
^
Error: Module did not self-register.
at Error (native)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object. (/Users/chyld/Code/temp/node_modules/gulp-sass/node_modules/node-sass/lib/index.js:211:15)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)

@DGStefan
Copy link

DGStefan commented Feb 8, 2015

Same here after upgrading nodejs to 0.12

@RichardLitt
Copy link

Same here.

@dlmanning
Copy link
Owner

For the record the problem here is with node-sass. It's not something I can fix. Follow this thread: sass/node-sass#653

@kylescousin
Copy link

Any estimate on when this will become compatible with 0.12?

@dlmanning
Copy link
Owner

@kylescousin : Please read my comment above

@sgade
Copy link

sgade commented Feb 11, 2015

I used the current node-sass master and built the binaries myself. That worked fine.
However, now I'm getting this in my gulp.task:

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.

@oliversong
Copy link

@dlmanning fyi looks like they updated node-sass to the next version which resolves the issue.

@mcshaman
Copy link

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.

@dlmanning
Copy link
Owner

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 npm install .

@mcshaman
Copy link

Didn't work for me

npm ERR! Darwin 14.1.0
npm ERR! argv "node" "/usr/local/bin/npm" "install"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE

npm ERR! node-sass@2.0.0 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the node-sass@2.0.0 postinstall script 'node scripts/build.js'.
npm ERR! This is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/build.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/username/project/node_modules/gulp-sass/npm-debug.log

@mcshaman
Copy link

Well I just updated to node-sass 2.0.1. The self-register error has gone... but now I have the following error

[20:24:47] Using gulpfile ~/project/gulpfile.js
[20:24:47] Starting 'sass'...
[20:24:47] Finished 'sass' after 7 ms
/Users/username/project/node_modules/gulp-sass/index.js:50
        obj.map.sources = obj.map.sources.map(function(source) {
                                         ^
TypeError: Cannot read property 'map' of undefined
    at opts.success (/Users/username/project/node_modules/gulp-sass/index.js:50:42)
    at options.success (/Users/username/project/node_modules/gulp-sass/node_modules/node-sass/lib/index.js:163:7)

Is this because of me or is it something else that needs fixing?

@mathiasbynens
Copy link

@mcshaman See #190.

@dlmanning
Copy link
Owner

Fixed in 314ce5c

@RichardLitt
Copy link

Thanks @dlmanning

@wdinau
Copy link

wdinau commented Feb 17, 2015

it works!! you're amazing @dlmanning

My old error:
Module._extensions extension (this, filename);
^
Error: Module did not self-register.

after using 1.3.3 it all works.

@dlmanning
Copy link
Owner

@wdinau Thanks, but all the credit here goes to the node-sass team.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.