The version 3.0.1 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 gulp-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 Notesv3.0.1
A relatively small maintenance release.
Fixes
If the error from UglifyJS contains column information, append this to the error message (alongside the line number).
Buffers are now allocated with Buffer.from, ensuring Buffers never have any private information.
The Streams callback is only called once, even if a downstream exits in error.
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 3.0.1 of gulp-uglify was just published.
The version 3.0.1 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 gulp-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
v3.0.1A relatively small maintenance release.
Fixes
Buffer.from
, ensuring Buffers never have any private information.Commits
The new version differs by 47 commits.
c92197d
3.0.1
27b26d4
fix(composer): invoke callback only once
2c7f656
tests: import tape-catch to catch thrown errors
b2492c4
fix: create safe-buffers
a751c5a
tests: convert tests to to tape harness
95f17a5
feat(error): add column to error string
e2462fa
chore(travis): update test matrix
14f1d71
docs(pump): correct grammar
845ae0f
chore(license): remove blockquote from license
9c7b1ae
docs(README): update links
76b5b3a
fix(package): update files array
5d4c4c6
chore(all): refactor unit tests
f2b779b
feat(composer): implement new API for composing deps
dbbba30
fix(minify): log warnings to gulplog
4cc8751
feat(uglify): add support for UglifyJS3
There are 47 commits in total.
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: