Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
This is a tracking issue for a post-MVP feature
WebAssembly programs are currently represented through a
While ES6 defines how to parse, link and execute a module, ES6 does not define when this parsing/linking/execution occurs. An additional extension to the HTML spec is required to say when a script is parsed as a module instead of normal global code. This work is ongoing.
Currently, the following entry points for modules are being considered:
Additionally, an ES6 module can recursively import other modules via
Any non-builtin imports from within a WebAssembly module would be treated as if they were
This integration strategy should allow WebAssembly modules to be fairly interchangeable with ES6 modules (ignoring GC/Web API
I'm interested in helping with this, although perhaps not quite championing.
It should be made by content-type determination.