Skip to content

Commit 52c1614

Browse files
committed
minor
1 parent 2d77cc2 commit 52c1614

File tree

1 file changed

+3
-3
lines changed
  • 1-js/13-modules/03-modules-dynamic-imports

1 file changed

+3
-3
lines changed

1-js/13-modules/03-modules-dynamic-imports/article.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,9 +25,9 @@ if(...) {
2525
}
2626
```
2727

28-
That's because, import/export aim to provide a backbone for the code structure. That's a good thing, as code structure can be analyzed, modules can be gathered and bundled together, unused exports can be removed (tree-shaken). That's possible only because everything is fixed.
28+
That's because `import`/`export` aim to provide a backbone for the code structure. That's a good thing, as code structure can be analyzed, modules can be gathered and bundled together, unused exports can be removed ("tree-shaken"). That's possible only because the structure of imports/exports is simple and fixed.
2929

30-
But how do we import a module dynamically, on-demand?
30+
But how can we import a module dynamically, on-demand?
3131

3232
## The import() function
3333

@@ -49,6 +49,6 @@ Like this:
4949
5050
[codetabs src="say" current="index.html"]
5151
52-
So, dynamic imports are very simple to use.
52+
So, dynamic imports are very simple to use, and they allow to import modules at run-time.
5353
5454
Also, dynamic imports work in regular scripts, they don't require `script type="module"`.

0 commit comments

Comments
 (0)