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

[greenkeeper]

Version 3.0.28 of uglify-js just got published.

Branch	Build failing 🚨
Dependency	uglify-js
Current Version	3.0.27
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.0.28

 

Commits

The new version differs by 3 commits.

• f81ff10 v3.0.28
• 16d4091 don't escape null characters as \0 when followed by any digit (#2273)
• e7c21e8 fix ie8 mangling of top-level AST_SymbolCatch (#2263)

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.27 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[redgeoff]

Replaced by #74