Add options.onEvent
, aiming to add event listeners to the build process.
#35
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.
In the case in
bundle
mode , if multiple entries reference the same style file, the generated CSS file will repeatedly include this style file.Here is a detailed example: In
test/repeat-css
, the components demo are referenced in bothpages/main
andpages/sub
, and it's clear that the style file of demo appears multiple times in the dist output.Therefore, I need to add event listeners (
options.onEvent
) during the build process to broadcast the input and output of each action in the build process through events. This will allow other plugins to further process the source data in the onEnd phase, such as separating CSS files into external files based on the import path.