This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of gulp-uglify.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
minifier: use UglifyJS 2.7.0's input map support (8160697)
BREAKING CHANGES
errors: Emitted errors are of a new type. Original UglifyJS
error message are preserved instead of the attempt to normalize them.
The constructor is exported as "GulpUglifyError" to allow for instance
checks.
minifier: Now requires UglifyJS 2.7.0 or greater to use the
input object support.
Coverage remained the same at 90.845% when pulling e8ef9ad396410f56832aac406e6888ce72e0680f on greenkeeper-gulp-uglify-2.0.0 into 215bfb9d9354a8e5851d87120b2e66fd2d4e37ec on master.
Hello lovely humans,
gulp-uglify just published its new version 2.0.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of gulp-uglify. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
Bug Fixes
GulpUglifyError
(1232c3c)gulplog
for the warning (5632cee)Features
BREAKING CHANGES
The new version differs by 77 commits .
e4f9045
2.0.0
566ec6a
refactor(tests): write tests with mocha
5651111
refactor(tests): replace
cmem
withtestdouble
b82387b
refactor(tests): compose streams with
mississippi
utilities1232c3c
fix(errors): emit errors of type
GulpUglifyError
5632cee
fix(minifer): use
gulplog
for the warning8160697
feat(minifier): use UglifyJS 2.7.0's input map support
3ec8fc3
chore(package): update uglify-js to version 2.7.0
a9c55b9
doc(README): spelling mistake in example
80da765
chore(release): 1.5.4
01fb8ca
chore(package): update uglify-js to version 2.6.4
8aa877e
chore(package): update uglify-js to version 2.6.3
0027093
chore(lint): resolve lint failures
fe2158a
chore(package): update xo to version 0.16.0
a03b663
docs(README): document how to minify (some) ES6
There are 77 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade