An in-range update of pretty-bytes is breaking the build 🚨

[greenkeeper]

The dependency pretty-bytes was updated from 5.1.0 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.

pretty-bytes is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
• ✅ coverage/coveralls: First build on greenkeeper/pretty-bytes-5.2.0 at 85.802% (Details).

---

Release Notes for v5.2.0

• Add TypeScript definition (#50) 44858ce

v5.1.0...v5.2.0

Commits

The new version differs by 2 commits.

• face5d9 5.2.0
• 44858ce Add TypeScript definition (#50)

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]

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

[greenkeeper]

• The dependency pretty-bytes was updated from 5.2.0 to 5.3.0.

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

Release Notes for v5.3.0

• Add bits option (#53) cb93e5b

v5.2.0...v5.3.0

Commits

The new version differs by 3 commits.

• 50f9fdb 5.3.0
• cb93e5b Add bits option (#53)
• cdc6ea7 Create funding.yml

See the full diff