An in-range update of bower is breaking the build 🚨

[greenkeeper]

Version 1.8.1 of bower just got published.

Branch	Build failing 🚨
Dependency	bower
Current Version	1.8.0
Type	devDependency

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

As bower 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/appveyor/branch AppVeyor build failed Details
• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

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 1.8.0 your tests are passing again. Downgrade this dependency 📌.

[greenkeeper]

Version 1.8.2 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

[greenkeeper]

Version 1.8.3 just got published.

Your tests are still failing with this version. Compare the changes 🚨

[greenkeeper]

Version 1.8.4 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Release Notes

v1.8.4

• Fixes release 1.8.3 by publishing with npm@3 instead of npm@5 (to include lib/node_modules)