Skip to content

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

@greenkeeper

Description

@greenkeeper

Version 3.0.25 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 3.0.24
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
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.0.25

 

Commits

The new version differs by 11 commits.

  • 4e12a6f v3.0.25
  • b35dfc2 reject malformed CLI parameters (#2239)
  • 9e1da92 ensure ie8 works with mangled properties (#2238)
  • a5ffe2c drop unused builtin globals under unsafe (#2236)
  • 9282e7b fix unsafe evaluate of Object static methods (#2232)
  • 5229cb2 drop unused compound assignments (#2230)
  • 458e3e1 enhance passes (#2229)
  • c615a1e fix gzip stream in test/benchmark.js (#2228)
  • 10a938c enhance source mapping on IIFEs (#2224)
  • 4956ad3 benchmark gzipped output (#2220)
  • 145874e docs: update benchmarks using node 8, add babili (#2218)

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 🌴

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions