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.
Recently a terser-webpack-plugin was released and based on a fact that
uglify-es
is no longer maintained and issues like #4711 and probably couple of more https://github.com/facebook/create-react-app/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+uglify+, I am opening this PR to start a potential discussion of moving toterser
.Terser retains API compatibility with
uglify-es
, so I just updated necessarypackage.json
andwebpack.config
files and didn't touch any options, however I am curious if this optionhttps://github.com/facebook/create-react-app/blob/next/packages/react-scripts/config/webpack.config.prod.js#L132
could be fixed by migration.
Closes #4711 and potentially more.