Update FAQ: I think it was meant "external" instead of "other-entry.js" #3756
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
external
is the one imported twice inmain.js
and later inother-entry.js
This PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
Description
In the question Why do additional imports turn up in my entry chunks when code-splitting? it was stated
In line 2 it should say "The import of external is already loaded and parsed" because
other-entry.js
is the one that importsexternal