Make sure that indirectly reexported modules also become chunk dependencies when preserving modules #3273
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.
This PR contains:
Are tests included?
Breaking Changes?
List any relevant issue numbers:
Resolves #3113
Description
This makes sure that when a module A imports a variable that is reexported by a module B from another module C in two steps, i.e. first imported and then exported, and all three involved modules end up in different chunks, then the chunk of C becomes an actual dependency of the chunk of A.
This was a problem when preserving modules as here, transitive dependencies were never hoisted and some exports were suppressed.