Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Webpack + Electron Forge + SQlite3 should work out of the box

See original GitHub issue

Preflight Checklist

I have read the contribution documentation for this project.
I agree to follow the code of conduct that this project follows, as appropriate.
I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details

Electron Forge Version:
- 6.0.0-beta.49
Electron Version:
- v7.1.7
Operating System:
- Windows 10 x64

Expected Behavior

Webpack should copy and use the Electron bindings from

node_modules\sqlite3\lib\binding\electron-v7.1-win32-x64\node_sqlite3.node

Actual Behavior

Webpack instead copies the original Node bindings and loads those, giving the usual Error: The module was compiled against a different Node.js version, with the following path:

node_modules\sqlite3\lib\binding\node-v79-win32-x64\node_sqlite3.node

To Reproduce

Configure Forge with webpack (I also use TypeScript), install sqlite3, import it in a script, and run the start script.

Additional Information

None

Issue Analytics

State:
Created 4 years ago
Comments:10 (4 by maintainers)

Top GitHub Comments

1reaction

deadcoder0904commented, Apr 26, 2020

@cyril-barragan In case you ever give electron-forge a shot again, then check this out

I found a working solution with electron-forge & better-sqlite3 & correct bindings are used 😃

1reaction

cyril-barragancommented, Apr 11, 2020

Yes I did but no luck either, I even set it as postinstall script. I ended up not using electron-forge and using only electron-webpack with electron-rebuild as postinstall script.