jonathanweiss/component-manager

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

greenkeeper opened this issue · 1 comments

greenkeeper commented

Version 3.0.5 of uglify-js just got published.

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

 

Commits

The new version differs by 9 commits0.

  • ff526be v3.0.5
  • e005099 fix & improve coverage of estree (#1935)
  • 504a436 Tweak README Notes (#1934)
  • 3ca9022 fix bugs with getter/setter (#1926)
  • fd09512 document 3 max passes (#1928)
  • 9e29b6d clarify wording (#1931)
  • c391576 remove support for const (#1910)
  • ac73c5d avoid arguments and eval in reduce_vars (#1924)
  • 547f41b add documentation for side_effects & [#@]__PURE__ (#1925)

false

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 🌴

jonathanweiss commented

Test result is false negative. Fixed with 6bea950