Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Note interaction with import assertions #45

Merged
merged 4 commits into from
Dec 2, 2021
Merged

Note interaction with import assertions #45

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
724adfa
note interaction with import assertions
guybedford Jan 15, 2021
2b996b6
include import assertions link
guybedford Jan 15, 2021
7eb8b02
wording
guybedford Jan 15, 2021
ae2ad8e
move to linking, clarify current status
guybedford Nov 19, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions proposals/esm-integration/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,14 @@ The ECMAScript specification holds the module's export in a lexical scope, as po

At the end of the link phase, the variables in the module's lexical scope are generally uninitialized. From JavaScript, accessing an uninitialized import causes a ReferenceError. JavaScript function declarations are initialized during the Link phase, as part of function hoisting, but WebAssembly function exports are not initialized until the Evaluation phase.

#### Import Assertions

[Import assertions](https://github.com/tc39/proposal-import-assertions) specify linking invariants that should be verified before evaluation can proceed. Currently HTML specifies a `"type"` assertion which is a requirement for CSS or JSON module imports due to their having different security privileges over full execution.

When importing WebAssembly from JavaScript, no assertion should be required since they share the same security privilege level in the ESM integration and in order to ensure transparent interoperability of the formats.

Future Wasm extensions may include supporting these assertions for imports from WebAssembly modules.

### Evaluate

During evaluation, the code is evaluated to assign values to the exported bindings. In JS, this means running the top-level module code.
Expand Down