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.

Sign up for GitHub

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

Jump to bottom

Update javascript-modules.md #94

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update javascript-modules.md #94

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion markdown/en/book/appendix/javascript-modules.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -415,7 +415,7 @@ We'll finish up this chapter with a brief look at [**dynamic imports**](https://

**Static imports use the `import` statement, while dynamic imports use the `import()` function.**

With dynamic imports you can optionally load a module during the execution of your code. This might be useful, for example, if you want to create an app that can load any of the [thirty or so 3D asset formats that three.js supports](https://github.com/mrdoob/three.js/tree/master/examples/jsm/loaders) (there are more than thirty loaders there, but some are for textures and other things). Altogether, these loaders comprise around one megabyte of JavaScript, which is a lot to force upon a poor user if they only need a fraction of it. Instead, you can wait until the user sends you a model file, examine the file and say, "_ayup, that there's an FBX file, better be fetchin' tha `FBXLoader`_":
With dynamic imports you can optionally load a module during the execution of your code. This might be useful, for example, if you want to create an app that can load any of the [thirty or so 3D asset formats that three.js supports](https://github.com/mrdoob/three.js/tree/master/examples/jsm/loaders) (there are more than thirty loaders there, but some are for textures and other things). Altogether, these loaders comprise around one megabyte of JavaScript, which is a lot to force upon a poor user if they only need a fraction of it. Instead, you can wait until the user sends you a model file, examine the file and say, "_ayup, that there's an FBX file, better be fetchin' that `FBXLoader`_":

{{< code lang="js" linenos="false" hl_lines="" caption="Dynamically importing the FBXLoader at run time" >}}

Expand Down