← back to v156 · deferred-imports-evaluation-import-defer
conformance · v156
v156 · deferred-imports-evaluation-import-defer — conformance probe
4 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
4
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
import-defer-grammar-parses |
The `import defer * as ns from "..."` grammar parses and evaluates: dynamically importing a module that uses it resolves instead of throwing a SyntaxError. spec ↗ | script | … | |
deferred-namespace-tostringtag |
A deferred module namespace object reports Symbol.toStringTag === "Deferred Module" (distinct from a normal namespace's "Module"). spec ↗ | script | … | |
evaluation-deferred-until-property-access |
A deferred module's top-level code does not run on import, is not triggered by a Symbol key read, and runs exactly once on the first string-property access on the namespace. spec ↗ | script | … | |
top-level-await-subtree-eagerly-evaluated |
A deferred subtree containing top-level await cannot be deferred: those async modules are evaluated eagerly during loading, leaving only the synchronous parts deferred. spec ↗ | manual | … |