This repository has been archived by the owner on Feb 9, 2024. It is now read-only.
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.
Hello lovely humans,
gulp-uglify just published its new version 3.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 ✨
You rock!
🌴
GitHub Release
We're now targeting UglifyJS3, if you need to continue to use UglifyJS2, you should stay on v2.1.2.
Breaking Changes
The custom option "preserveComments" was removed.
As a replacement, set the
options.output.comments
option directly, UglifyJS3 understands the following options:While the "some" option works for many cases, it doesn't fully match the behavior of the "license" option. Fortunately, you can pass the exported function from
uglify-save-license
as the comment option.The "minifier" API, which you could use to provide your own UglifyJS instance has been removed. It has been replaced with the "composer" API.
The new version differs by 28 commits .
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
ad73ab8
chore(pkg): update dependencies, run lint
4656fe5
2.1.2
ba83a45
fix(package): move eslint dependencies to dev
3d0f155
2.1.1
c722ab9
fix(errors): restore file and line info
da3e18f
chore(prettier): setup prettier
ec8ba54
fix(tests): UglifyJS errors use "message" property
6c336ec
v2.1.0
35c33f1
chore(uglifyjs): loosen uglify-js pin
74b6eff
2.0.1
There are 28 commits in total. See the full diff.