Support emitting files via manualChunks in output #4761
Merged
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:
Description
This changes the logic for emitting files to handle files emitted during output generation phase via a transform hooks that is triggered for the first time by the
manualChunks
option of that output. This may not be exactly what users expect, but it is difficult to differentiate legitimate uses of the file emitter from illegitimate uses, especially with new features in the pipeline.As a follow-up, it would be worthwhile to add a way for assets to obey tree-shaking in so far that assets that are never referenced are not emitted.