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

[greenkeeper]

The devDependency np was updated from 5.1.3 to 5.2.0.

🚨 View failing branch.

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

np is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).
• ❌ Travis CI - Branch: The build errored.

---

Commits

The new version differs by 6 commits.

• b67cdb4 5.2.0
• 7d7900a Update dependencies
• 000ddcf Don't check "files" in package.json or .npmignore if private package or not publishing (#472)
• 23524b5 Don't ask for tag if --no-publish (#473)
• 8360cb6 Check package name availability in custom registry (#429)
• e53cbe8 Fix incorrectly showing "Aborted!" message on successful publish (#471)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

• The devDependency np was updated from 5.1.3 to 5.2.1.

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

[greenkeeper]

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