Update to Emscripten 3.1.64

[cxcorp]

This PR upgrades Emscripten to 3.1.64 and fixes things caused by breaking Emscripten changes.

• 3.1.52 no longer allows using .bc, so use .o instead in Makefile. Using .a throws "Unknown format, not a static library!".
• 3.1.55 no longer supports --memory-init-file so removed from Makefile

I don't have the capacity to do further testing other than just checking that the repo's npm run test passed, and don't have enough context about the repo to know what's breaking in the changelog so I'll just leave this work here in case it's useful.

Closes #588

[cxcorp]

While testing this with the devcontainer, I bumped into puppeteer/puppeteer#12833 which I workarounded with

diff --git a/.devcontainer/devcontainer.json b/.devcontainer/devcontainer.json
index ce6189c..072317b 100644
--- a/.devcontainer/devcontainer.json
+++ b/.devcontainer/devcontainer.json
@@ -20,7 +20,7 @@
        // Use 'postCreateCommand' to run commands after the container is created.
        // We use `npm ci` instead of `npm install` because we want to respect the lockfile and ONLY the lockfile.
        // That way, our devcontainer is more reproducible. --Taytay
-       "postCreateCommand": "npm ci",
+       "postCreateCommand": "PUPPETEER_DOWNLOAD_BASE_URL=https://storage.googleapis.com/chrome-for-testing-public npm ci",
        // Comment out connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
        "remoteUser": "node"
 }
\ No newline at end of file

with the proper fix being upgrading Puppeteer. Puppeteer's postinstall step still tries to download the correct version of Chrome so might as well delete the chrome installation from the devcontainer (although the fonts-freefont-ttf package is needed to render fonts though, I think).

[cxcorp]

Some warnings in CI:

warning: JS library symbol '$ALLOC_NORMAL' is deprecated. Please open a bug if you have a continuing need for this symbol [-Wdeprecated]
warning: JS library symbol '$ALLOC_STACK' is deprecated. Please open a bug if you have a continuing need for this symbol [-Wdeprecated]
warning: JS library symbol '$allocate' is deprecated. Please open a bug if you have a continuing need for this symbol [-Wdeprecated]
warning: JS library symbol '$allocateUTF8OnStack' is deprecated. Please open a bug if you have a continuing need for this symbol [-Wdeprecated]
emcc: warning: warnings in JS library compilation [-Wjs-compiler]

I think these come from e.g.: https://github.com/emscripten-core/emscripten/blob/8c81cac1bbae378bc7dde0c21c99602cbaf452d0/src/library_legacy.js#L12-L16

will probably become an upgrade blocker at some point but not right now

[lovasoa]

Thank you!

[vwh]

Thank you!

This pull request broke the https://sql.js.org/dist/sql-wasm.wasm build
I had to use older WASM build to fix it

[cxcorp]

It looks like the main branch's CI deploys the dist to GitHub Pages, so the sql-wasm.wasm hosted there is from the main branch which is probably not backwards compatible with the sql-wasm.js from npm, as emscripten makes no ABI compatibility guarantees across versions. Using https://sql.js.org/dist/sql-wasm.js works at least with the docs' web demo.

[lovasoa]

Ok, I'll make a new release on npm

[lovasoa]

I updated puppeteer in 158dfb4

[lovasoa]

I just pushed v1.11.0 which is compatible with the wasm file from sql.js.org