-
Notifications
You must be signed in to change notification settings - Fork 40
uglify-js@2.8.10 breaks build 🚨 #155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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,
uglify-js just published its new version 2.8.10.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As uglify-js is "only" a devDependency of this project it might not break production or downstream projects, but "only" your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
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 210 commits .
e9920f7v2.8.107e465d4scan RHS of dropped assignments (#1581)aa80ee3remove checkboxes from Issues template80e8176explain how to make a proper bug report (#1579)711f88dscan assignment value in drop_unused() (#1578)344d11dv2.8.9c7cdcf0fix function name eliminiation (#1576)3ee5574only run benchmark & jetstream on CI (#1571)dedbeefplan B for IE8 do-while semi-colon fix (#1572)bd6dee5fix return from recursive IIFE (#1570)144052cv2.8.865c848cinclude benchmark.js in test suite (#1564)8a8a94afix deep cloning of labels (#1565)8153b7btransform function calls to IIFEs (#1560)d787d70avoid substitution of global variables (#1557)There are 210 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.