An in-range update of uglify-js is breaking the build 🚨

[greenkeeper]

Version 3.1.0 of uglify-js just got published.

Branch	Build failing 🚨
Dependency	uglify-js
Current Version	3.0.28
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

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 💪

Status Details

• ❌ ci/circleci Your tests failed on CircleCI Details

---

Release Notes

v3.1.0

 

Commits

The new version differs by 9 commits.

• cd27f4e v3.1.0
• 8158b1b Testing all leading comments against being PURE comments (#2305)
• aacf3ed extend unsafe on pure global functions (#2303)
• 8b89072 add Date and other known globals to unsafe compress option (#2302)
• 395a17c fix collapse_vars on default function argument (#2299)
• 3f35586 correctly count declarations after hoist_vars (#2297)
• 71d52f1 Fix CLI example for mangle reserved list of names (#2294)
• eb7adaa Fix CLI source-maps examples (#2291)
• e5cf797 fix unused patching of AST_For.init blocks (#2289)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 3.0.28 your tests are passing again. Downgrade this dependency 📌.

[redgeoff]

Fixed by #78