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.

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

Note interaction with import assertions #45

Merged
merged 4 commits into from
Dec 2, 2021
Merged
Changes from 3 commits
Commits
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
6 changes: 6 additions & 0 deletions proposals/esm-integration/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,6 +122,12 @@ Some impacts of reading the imports up-front:

See the FAQ for more explanation of the rationale for this design decision, and what features it enables which would be difficult or impossible otherwise.

### Import Assertions

When integrating with the [Import Assertions proposal](https://github.com/tc39/proposal-import-assertions), it is important to note that `assert { type: 'wasm' }` will not be supported, because there is no privilege escalation between ESM imports or Wasm imports.

Instead, the ESM integration may take advantage of [evaluator attributes](https://github.com/tc39/proposal-import-assertions#follow-up-proposal-evaluator-attributes) in future in order to potentially permit features such as instance constructors or private Wasm imports.

## FAQ

### How would this work, in some concrete examples?
Expand Down