Skip to content

Commit 0275704

Browse files
authored
ch08: Fix footnote (#72)
1 parent 7f9241c commit 0275704

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

ch08.asciidoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -520,7 +520,7 @@ console.log(counter.default) // <- 2
520520

521521
==== Dynamic import()
522522

523-
At the ((("dynamic import()", id="di8")))((("ES6 modules", "dynamic import()", id="esm8di")))time of this writing, a proposal for dynamic ++import()++pass:[<span class="footnote">Check out the <a href="https://mjavascript.com/out/dynamic-import">proposal specification draft</a>.</span>] expressions is sitting at stage 3 of the TC39 proposal review process. Unlike `import` statements, which are statically analyzed and linked, `import()` loads modules at runtime, returning a promise for the module namespace object after fetching, parsing, and executing the requested module and all of its dependencies.
523+
At the ((("dynamic import()", id="di8")))((("ES6 modules", "dynamic import()", id="esm8di")))time of this writing, a proposal for dynamic ++import()++pass:[<span data-type="footnote">Check out the <a href="https://mjavascript.com/out/dynamic-import">proposal specification draft</a>.</span>] expressions is sitting at stage 3 of the TC39 proposal review process. Unlike `import` statements, which are statically analyzed and linked, `import()` loads modules at runtime, returning a promise for the module namespace object after fetching, parsing, and executing the requested module and all of its dependencies.
524524

525525
The module specifier can be any string, like with `import` statements. Keep in mind `import` statements only allow statically defined plain string literals as module specifiers. In contrast, we're able to use template literals or any valid JavaScript expression to produce the module specifier string for `import()` function calls.
526526

0 commit comments

Comments
 (0)