feat: make the minimizer config available in all modes #4641
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As long as the `minimize` option is set to false (which is default in production mode), the code won't be minimized. So the mode doesn't matter when it comes to the `minimizer` config. By exposing this config, users can simplify their custom config, by removing the `process.env.NODE_ENV === 'production'` guard around their custom minimizer configuration.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As long as the
minimizeoption is set to false (which is default inproduction mode), the code won't be minimized regardless of the
minimizerconfig's presence.By exposing this config, users can simplify their custom config, by
removing the
process.env.NODE_ENV === 'production'guard around theircustom minimizer configuration.
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
Other information: