This repository has been archived by the owner on Feb 12, 2022. It is now read-only.
Update grunt-contrib-uglify to version 2.0.0 🚀 #1846
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
e853015 to
64d30d0
Compare
|
Might be useful, need to research whats different in Uglify 2 and if it breaks the dist files in any way. |
64d30d0 to
220e83a
Compare
cmcculloh-kr
approved these changes
Sep 22, 2016
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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,
grunt-contrib-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 grunt-contrib-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!
🌴
The new version differs by 12 commits .
2d04f24Update uglify to v2.7.0. (#416)48285c9Reduce lodash usage. (#422)0d2f331Used grunt.verbose to show detailed logging (#419) r=vladikoffc3dae35v1.0.2. (#423) r=vladikoffc2d695fReport option:falsevalue is not supported.3150ca2Merge pull request #418 from gruntjs/beautify-obj5923f5bFixbeautifywhen passed as an object.5fc442fUpdate test files for the latest 2.6.4 version.a428a24Update CI configs from the latest grunt-contrib-internal.f680e89Upgrade grunt and devDeps to 1.07e72c39Update docs.bd4d1e4Update CHANGELOG.See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade