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

[greenkeeper]

Version 2.2.0 of feathers just got published.

Branch	Build failing 🚨
Dependency	feathers
Current Version	2.1.7
Type	devDependency

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

As feathers 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

• ✅ codeclimate/coverage 97.18% Details
• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Commits

The new version differs by 7 commits.

• aa87658 2.2.0
• 1738993 Update package-lock.json
• 7422757 No longer pollutes the global scope (#662)
• a28ec8e fix(package): update debug to version 3.0.0 (#641)
• e317dd5 Examples url is tinny (broken) (#634)
• b57c80b Merge pull request #624 from jansel369/master
• 8f40769 Adds a missing configure() method in typescript difinition

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