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 doesn't work on Windows with io.js v2.0.x #449

Closed
v12 opened this issue May 13, 2015 · 5 comments
Closed

Module doesn't work on Windows with io.js v2.0.x #449

v12 opened this issue May 13, 2015 · 5 comments

Comments

@v12
Copy link

v12 commented May 13, 2015

Hello there,

I'm experiencing an issue with sqlite3 module usage on Windows 8.1 x64 machine, though everything is absolutely fine with similar setup on Linux.

npm i sqlite3 output - gist

As you can see, installation via npm went fine, however, when I try to use the module in the code, I get the following error:

module.js:356
  Module._extensions[extension](this, filename);
                               ^
Error: Module did not self-register.
    at Error (native)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at Object.<anonymous> (C:\Dev\projects\sqlite3-test\node_modules\sqlite3\lib\sqlite3.js:4:15)
    at Module._compile (module.js:431:26)
    at Object.Module._extensions..js (module.js:449:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)

io.js versions tested: v2.0.0 and v2.0.1
sqlite3 version is v3.0.8

Let me know if you require any additional information.

@v12 v12 changed the title Module doesn't on Windows with io.js v2.0.x Module doesn't work on Windows with io.js v2.0.x May 13, 2015
@magicdawn
Copy link

same on iojs@1.6.3

@springmeyer
Copy link
Contributor

Thanks for the report. Just seeing this now. Two problems:

  1. Ideally a source compile should not be needed. Turns out I made a mistake in packaging and the binary is missing. Going to work on that in missing node-v44 binary for windows #469
  2. ^^ the binary might be missing because of the problem you are hitting Module did not self-register. Will need some time to recall what might cause this.

nodejs/node#751 looks like it was a mis-configuration and is not a bug/the cause of this conclusively. However nodejs/node#751 might be involved.

@springmeyer
Copy link
Contributor

Anyone hitting this should be able to workaround it by using node v0.10.x or v0.12.x.

@novacrazy
Copy link

Downgrading is not an option for me, what else can you suggest for using this library?

@daniellockyer
Copy link
Member

Please try with the latest version - v5.0.3 🙂

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

No branches or pull requests

7 participants
@springmeyer @ErisDS @daniellockyer @v12 @magicdawn @novacrazy and others