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 FAQ: I think it was meant "external" instead of "other-entry.js" #3756

Merged
merged 2 commits into from Sep 1, 2020
Merged

Update FAQ: I think it was meant "external" instead of "other-entry.js" #3756

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3f0c83f
Update faq: other-entry.js -> external
madacol Sep 1, 2020
a1fcb97
Update docs/06-faqs.md
madacol Sep 1, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/06-faqs.md
View file
Open in desktop
Expand Up @@ -58,7 +58,7 @@ This does not affect code execution order or behaviour, but it will speed up how

With this optimization, a JavaScript engine will discover all transitive dependencies after parsing an entry module, avoiding the waterfall:
1. Load and parse `main.js`. At the end, imports to `other-entry.js` and `external` will be discovered.
2. Load and parse `other-entry.js` and `external`. The import of `other-entry.js` is already loaded and parsed.
2. Load and parse `other-entry.js` and `external`. The import of `external` from `other-entry.js` is already loaded and parsed.
3. Execute `main.js`.

There may be situations where this optimization is not desired, in which case you can turn it off via the [`output.hoistTransitiveImports`](guide/en/#outputhoisttransitiveimports) option. This optimization is also never applied when using the [`output.preserveModules`](guide/en/#outputpreservemodules) option.
Expand Down