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

Error: Module did not self-register. with Node 0.12 installed #653

Closed
sjonnet19 opened this issue Feb 7, 2015 · 42 comments
Closed

Error: Module did not self-register. with Node 0.12 installed #653

sjonnet19 opened this issue Feb 7, 2015 · 42 comments

Comments

@sjonnet19
Copy link

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. (/vagrant/uil/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)
Makefile:50: recipe for target 'debug' failed
make: *** [debug] Error 1

@am11 am11 mentioned this issue Feb 7, 2015
@am11 am11 added the v2 label Feb 7, 2015
@am11
Copy link
Contributor

am11 commented Feb 7, 2015

node.js v0.12 (which was released 22 hours ago) will be supported by node-sass' next version v2.0.0.

@emiltsokov
Copy link

any idea for a release date of version v2.0.0 ?

@am11
Copy link
Contributor

am11 commented Feb 7, 2015

@chemicalbr see #602.

@sjonnet19
Copy link
Author

Note that was 2.0.0 beta

@am11
Copy link
Contributor

am11 commented Feb 8, 2015

@sjonnet19, yes whenever the NODE_MODULE_VERSION changes, it require recompilation of binaries. See #627 (comment). That said; you can always manually build the binary (or by setting SKIP_SASS_BINARY_DOWNLOAD_FOR_CI environment variable to true before npm install node-sass <- given you have all the required tools installed).

@samccone
Copy link
Contributor

samccone commented Feb 8, 2015

👍 running into this on https://github.com/marionettejs/marionettejs.com

@xzyfer
Copy link
Contributor

xzyfer commented Feb 9, 2015

@Martii in future please use the subscribe button on the right ;)

@Martii
Copy link

Martii commented Feb 9, 2015

oh kewl... look there all the time and missed that sorry.

@demisx
Copy link

demisx commented Feb 9, 2015

+1 Same issue on node v0.12.0

@findfly618
Copy link

+1.....

@Vincz
Copy link

Vincz commented Feb 11, 2015

+1

1 similar comment
@dawidk92
Copy link

+1

@am11
Copy link
Contributor

am11 commented Feb 11, 2015

BTW, with current state of master, you can build the binary by yourself for node-sass .12 or io.js:

git clone https://github.com/sass/node-sass --recursive
cd node-sass
git submodule update --init --recursive
npm install
node node_modules/pangyp/bin/node-gyp rebuild -f
# or:
iojs node_modules/pangyp/bin/node-gyp rebuild -f

(Optionally you can configure before build: node node_modules/pangyp/bin/node-gyp configure .. then build or rebuild)

@patrickskim
Copy link

@am11 thanks for the tip.

@etmoore
Copy link

etmoore commented Feb 11, 2015

Installing node v.0.10 with nvm is a quick fix for those of you stuck on this issue.

@xzyfer
Copy link
Contributor

xzyfer commented Feb 12, 2015

Ah cool. There a second problem where weren't normalising the path we fetch the binary from. We didn't account for *nix returning nodejs where osx and windows return node. So *nix installs were failing to pull the binding and potentially breaking installs.

@am11
Copy link
Contributor

am11 commented Feb 12, 2015

@xzyfer, thanks for the quick fixes!

v2.0.1 is published with the fixes.

npm install node-sass@2.0.1

@samccone
Copy link
Contributor

@am11 thanks so much for the great work and the great lib

@jskungfu
Copy link

The issue seems to be appearing again with 2.1.1 and node.js 0.12.X.
When I downgraded node.js version to 0.10.38 - it started working fine. Any thoughts on how to resolve this issue with latest node version/io.js?

@caseywebdev
Copy link

@jskungfu I've been using node-sass successfully on 2.1.1 and 0.12.2. Have you tried clearing out node_modules and reinstalling?

@jskungfu
Copy link

@caseywebdev
I should have mentioned it with my original comment but I am mentioning it is now that I am using this as node module in my grunt watch task and it is working when first file change is noticed. After first successful compilation it starts giving me this error on consecutive compilations.

I tried to use all of above tricks that is mentioned above but it is not working with node 0.12.2 but when I switch back to node version 0.10.38, it works flawless with every file change compilations.

@xzyfer
Copy link
Contributor

xzyfer commented Apr 20, 2015

@jskungfu can you please create a new folder in ~/tmp. Run npm install@2.1.1 and confirm the issue still exists?

Please also supply us with your OS, OS version, and the output ./node_modules/.bin/node-sass --version.

@xzyfer
Copy link
Contributor

xzyfer commented Apr 20, 2015

As for your watching issues, that needs to be opened with the grunt-sass project.

@quarkasingh
Copy link

for me it resolved after 'npm rebuild'

@deepakskandari87
Copy link

Hi
I have a same issue when i run ./licode/scripts/initLicode.sh a log file is generated with bellow error
and in browser console i got message
...
DEBUG: Event: room-connected
erizo.js:161 ERROR: Error when publishing the stream: No ErizoAgents available

module.js:356
Module._extensions[extension](this, filename);
^
Error: liberizo.so: cannot open shared object file: No such file or directory
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/opt/licode/erizo_controller/erizoJS/erizoJSController.js:3:13)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
Please any one help me

@dipak8959
Copy link

Try : npm install --update-binary . It worked for me.

jiongle1 pushed a commit to scantist-ossops-m2/node-sass that referenced this issue Apr 7, 2024
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

No branches or pull requests