-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Consider removing manual modularization #438
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
Comments
Yes, this could be nice, and simplify our old build process. Are you interested in making a PR ? |
I'm thrilled to hear that this was fixed in Emscripten directly. I've been out of this project for a while, but am dipping my toes back in and can take a look if no one beats me to it. |
I don't know how the bug was originally triggered, but I tried adding Then to load the module in my page I did:
It seems to work. I'm using emsdk 2.0.16. Again, I don't know if I'm exercising the problem path. |
This makes an ES6 Module for SqlJs, not sure how it affects the other generated files. Based on Roy's comment sql-js#438 (comment) import initSqlJs from 'URL TO /sql-wasm.mjs'; const SQL = await initSqlJs({ // Required to load the wasm binary asynchronously. Of course, you can host it wherever you want // You can omit locateFile completely when running in node locateFile: file => `URL TO /sql-wasm.wasm` });
The generated code in
sql-wasm.js
mentions Emscripten issue: emscripten-core/emscripten#5820.This issue was fixed in PR emscripten-core/emscripten#10697 and released as version 13.9.16 in May 2020.
I think removing manual modularization will simplify sql.js build process.
The text was updated successfully, but these errors were encountered: