Introduced this type identifier to avoid copy-pasting it around

Unfortunately, I couldn't find a way in the new version of Emscripten to keep the old approach of using template metaprogramming to avoid this boilerplate. I tried with both ChatGPT and Claude Code and eventually just settled for using the boilerplate for now. We can always bring back a smarter approach later if we're able to figure it out

The output file now uses ESM instead of CommonJS. Our Jest pipeline normally transpiles ESM, but not for WASM files. Relevant Jest docs for enabling ESM

Emscripten was printing an error and I found online that the error meant it wanted a .o file instead of a .bc file

--memory-init-file 1 was previously ignored and --memory-init-file 0 was the implicit behavior. To avoid confusing people, emcc now errors when --memory-init-file is passed at all

Here are some sources from Claude:

1. GitHub Issue: https://github.com/emscripten-core/emscripten/issues/10622 - This GitHub issue discusses how memory init file generation is ignored in the WASM backend.
2. Stack Overflow: https://stackoverflow.com/questions/78203093/the-memory-init-file-is-no-longer-supported - A 2024 Stack Overflow question specifically about this error.
3. Panda3D Forum: https://discourse.panda3d.org/t/the-memory-init-file-is-no-longer-supported-emscripten/29978 - Another 2024 report of this issue.

This flag is no longer supported. Instead this diff updates the code to support ESM for the WASM JS file

The old version of Emscripten would output JS that importing a WASM file with underscores instead of dashes for some reason. It no longer has this issue

I don't see the point of having sed create this backup file and then immediately delete it, so I simplified the code a bit

Both the old and new Emscripten had the JS wrapper return a function that returns the module. But the new Emscripten outputs returns a Promise instead of returning the module immediately

The new Emscripten doesn't convert vectors to arrays, and instead has a special Emscipten vector type, which requires wrapping the calls with our own wrapper

The new Emscripten crashes when you pass null in for an optional<string> with Cannot pass non-string to std::string. I updated the types so they only take undefined, and I updated both tests and production pathways to pass undefined

This was a mistake in the test. If you look at beforeEach (and just the name messageWithNullFutureType itself) you can see that it was previously expected to be null, which I guess matches Jest's toBeDefined. It started erroring when I switched to undefined, which highlighted the error

We do some runtime conversions in the functions below to make sure we don't pass null to Emscripten for an std::optional (it only accepts undefined). I considered percolating the type narrowing upstream, but in this case, the types we're converting from are not web-specific, and it would've required updating SQLiteAPI types as well

Without this line we were getting an error during Webpack build:

Module not found: Error: Can't resolve 'module' in '/home/comm/app/web/shared-worker/_generated'

Moved this type to web/shared-worker/utils/sql-query-executor-wrapper.js