The version 4.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of rollup-plugin-uglify.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notesv4 and back to es5
uglify-es is not supported anymore so we returned back to old school uglify-js. If you still want to transpile es6+ try rollup-plugin-terser. Terser is actively developed fork of uglify-es with the new name.
In this version we changed the way to import plugin. Now it looks like this
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
Version 4.0.0 of rollup-plugin-uglify was just published.
rollup-plugin-uglify
The version 4.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of rollup-plugin-uglify.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v4 and back to es5uglify-es is not supported anymore so we returned back to old school uglify-js. If you still want to transpile es6+ try rollup-plugin-terser. Terser is actively developed fork of uglify-es with the new name.
In this version we changed the way to import plugin. Now it looks like this
To see more prettier errors uglify shows also babel code frame
Commits
The new version differs by 6 commits.
a847d2e
4.0.0
cd8f9f1
Change default export to named one
6e46a12
Use uglify-js as uglify-es got deprecated in favour of terser (#42)
3beec87
Merge pull request #40 from kzc/patch-1
5c07826
have README point to uglify-es docs
3dc7600
Fix tests
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: