Support ES Module Integration Proposal

[dsherret]

Deno 2.1 added support for standard Wasm modules (though there was a bug where it was missing exports like memory, though that's now fixed in the latest canary version deno upgrade canary or in the released version if this is being read after November 28th).

https://docs.deno.com/runtime/reference/wasm/#wasm-modules

It would be really cool to have support for it in wasm-bindgen because it would mean that the .wasm files would be part of the module graph, so remote Deno modules wouldn't need to do orchestration for downloading and caching the wasm files anymore.

Since Wasm modules are implemented in a standard way in Deno (or at least should be 😅), this should translate to having support for the browser as well.

Edit: Or I guess this is the "bundler" output? I didn't test yet if it works with imports.

[daxpedda]

Edit: Or I guess this is the "bundler" output? I didn't test yet if it works with imports.

Unfortunately I have absolutely no idea about Deno or the bundler output. I will also have a hard time reviewing something I absolutely have no understanding of.

In conclusion: I'm happy to do my best to review fixes to existing targets, but adding a new target is out of the cards unless someone steps up and offer long-term maintenance for that target in wasm-bindgen.

[dsherret]

I renamed the title. This is not Deno specific. It's just standard Wasm imports (which is the future and more ergonomic because the Wasm module is part of the module graph). It feels like something this project would want to support? It would allow dropping a bunch of the outputs in the future.

https://github.com/WebAssembly/esm-integration/blob/main/proposals/esm-integration/EXAMPLES.md

[daxpedda]

That's definitely in scope.