esm-integration
esm-integration copied to clipboard
WebAssembly
ECMAScript module integration
A trivial fix to the wording about how WebAssembly functions imported from JavaScript are treated.
As per the title, the basic case is like: ``` //a.js import {someFunc} from someModule.wasm someFunc(); ``` ``` //b.js import {someFunc} from someModule.wasm someFunc(); ``` ``` //c.js import a.js import...
There's been some feedback provided recently that toolchains and bundlers wouldn't be able to take advantage of the current Wasm/ESM integration proposal design, because it focuses on providing *instantiated* Wasm...
For example, if we modify the function import example and make `getCount` async. ```wasm ;; main.wat --> main.wasm (module (import "./counter.js" "getCount" (func $getCount (func (result i32)))) ) ``` ```js...
The current `fetch` approach of loading a wasm module allows you to track the progress of the (often large) network resource, and indicate its progress to the user (you just...
This is a tracking issue for the phase requirements and other issues that should be resolved for the proposal. **Phase 2 requirements** * [X] Full proposed English spec text available...
As far as I'm aware, when the original WebAssembly JS API was developed the ES module spec namespace exotic object had not been fully defined, thus `exports` was created as...
This proposal lets WebAssembly import JS modules just as much as it lets JS import WebAssembly modules. The idea is that they're all part of the same big module graph....
Now that [import assertions](https://github.com/tc39/proposal-import-assertions) are Stage 3, we have to decide how they will integrate with Wasm/ESM integration. There are two aspects of this: - When importing a Wasm module...
Somewhat related to https://github.com/WebAssembly/esm-integration/issues/41, it's worth thinking about what CSP policies will apply to the ESM integration when importing Wasm. Currently the [Wasm CSP spec](https://github.com/WebAssembly/content-security-policy/blob/master/proposals/CSP.md) defines `wasm-unsafe-eval` to be required...