Skip to content
This repository has been archived by the owner on Aug 29, 2021. It is now read-only.

Commit

Permalink
doc: remove reference to import-maps
Browse files Browse the repository at this point in the history
import-maps are no longer aiming to support fallbacks, at leas in the
initial implementation. We should remove the reference in the explainer

Refs: WICG/import-maps#176
  • Loading branch information
MylesBorins committed Oct 1, 2019
1 parent 99370fd commit 12f18d4
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -178,8 +178,6 @@ try {
}
```
Some kinds of dependency fallbacks may be handled by [import maps](https://github.com/wicg/import-maps), but even with the support of import maps, [some scenarios](https://github.com/WICG/import-maps/blob/master/README.md#alternating-logic-based-on-the-presence-of-a-built-in-module) which are outside of the declaratively handled set would still benefit from top-level `await`.
### WebAssembly Modules
WebAssembly Modules are "compiled" and "instantiated" in a logically asynchronous way, based on their imports: Some WebAssembly implementations do nontrivial work at either phase, which is important to be able to shunt off into another thread. To integrate with the JavaScript module system, they will need to do the equivalent of a top-level await. See the [WebAssembly ESM integration proposal](https://github.com/webassembly/esm-integration) for more details.
Expand Down

0 comments on commit 12f18d4

Please sign in to comment.