fix: should disconnect children correctly when remove available modules #10503
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.
Summary
fix #10320
When a chunk has some modules removed, should disconnect its AsyncDependencies as well.
For example giving the following chunk graph, you can see the test case for detail
The
routes.jsexists in bothmainandrouteschunk, the chunk graph looks just like aboveWhen removing available modules, the
routes.jsshould be removed fromrouteschunk, and thenrouteschunk should not containroutes.js, therouteschunk should not have a child of chunkfooBefore
After
Checklist