Error: Module did not self-register while using native node module
See original GitHub issueI am using webworker-threads and compiled WebWorkerThreads.node with exact the same node version pkg packaged the exececutable (v6.10.3). Do I miss some todo(s) else anywhere to use a native module? I also tried pkg . -boption with the same result.
Issue Analytics
- State:
- Created 6 years ago
- Comments:36 (3 by maintainers)
Top Results From Across the Web
Uncaught Error: Module did not self-register - Stack Overflow
Firstly, try npm rebuild . If your C++-add-on-based packages have a build script, it'll do. If it doesn't, you need ...
Read more >Error:Module did not self-register ---node-addon-examples
It is possible that multiple node / npm versions exist in your system that are causing trouble here.
Read more >Fix the Module did not self-register error in Node.js - Reactgo
This error occurs when a node_modules folder is corrupted in your project. Due to the network interruption or other reasons like some of...
Read more >Error: Module did not self-register couchbase - Node.js SDK
First, in node_modules/couchbase/build/Release you should find the built module. Run ldd/otool or like tools to see if there is something it ...
Read more >Writing Native Node.js Modules - RisingStack Engineering
_makeLong(filename)); ^ Error: Module did not self-register. From now on when you see this error you'll know what to do. Compiling our native...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
OK, it’s kind of funny but for us the solution was to rename the generated executable to node.exe. The inspiration comes from here. See “Native modules”.
It might be a good idea to either solve it or at least mention it in the documentation.
I’m having a similar problem, but with edge-js:
Versions:
Did you solve this issue @igorklopov ?