search

jonathanweiss / component-manager

Micro utility (583 bytes compressed) that manages initialising and teardown of components (e.g. jQuery plugins) as soon as specific DOM nodes are added into the document, respectively removed from it.
MIT License
7 stars 0 forks source link

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

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 3.0.22 of uglify-js just got published.

Branch Build failing 🚨
Dependency uglify-js
Current Version 3.0.21
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 :muscle:

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/jonathanweiss/component-manager/builds/248648344?utm_source=github_status&utm_medium=notification)
Release Notes v3.0.22

 

Commits

The new version differs by 2 commits.

  • 7659ea1 v3.0.22
  • bdeadff improve usability of name cache under minify() (#2176)

See the full diff

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

After pinning to 3.0.21 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

jonathanweiss commented 7 years ago

Fixed with c585c43d01bf818342223b123de1b46bda04a706