Before landing, I'll make sure we don't execute this twice

I modeled this after jsURL instead of olmFilename and sqljsFilename. The filename approach works well with Emscripten's locateFile utility, but not so well with wasm-bindgen (which has less tooling overall)

We don't await here, which means that we'll execute initOpaque but ignore the result. This is good because it makes sure we start downloading the WASM as soon as possible. Note that we'll still need to call await initOpaque(); before executing any calls on the WASM

Now that we're using --target web, initOpaqueKe(opaqueURL) is all we really need. The rest of the code here makes sure we only ever call that once

This is pulled from wasm-bindgen's TS output, with some slight modifications for Flow

I typed this as mixed because it actually returns some sort of wasm object with a bunch of internal stuff. My impression is that we shouldn't use it directly, so I'm using mixed as a "opaque type" (basically telling the caller they can't really do anything with it)

If we just say "@commapp/opaque-ke-wasm": "^0.0.3", yarn pulls it from our monorepo instead of using the published package. That's a problem because our monorepo doesn't have the built files, and we'd rather than affect the DevX by adding the build here to our build process. Instead we use this npm: alias to make sure the published package is used

TS output: https://gist.github.com/jonringer-comm/cab0614fdb54ac00b5f7692d0ae2ea2e