change from uglify to terser #937
Merged
Conversation
This file contains 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
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.
The uglify webpack plugin appears to have breaking changes, webpack-contrib/uglifyjs-webpack-plugin#362, and will not be supported for Webpack 5. Switching to terser appears to resolve the issue. No additional configuration was provided in the PR, however it may be worth considering additional configuration in the future.
This also fixes removes an unused setting for the devtool and moves that configuration to the bottom, and switches to a tool that will compile faster and keep the source map. https://webpack.js.org/configuration/devtool/