An in-range update of big.js is breaking the build 🚨

[greenkeeper[bot]]

The dependency big.js was updated from 5.1.2 to 5.2.1.

🚨 View failing branch.

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

big.js 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 is in progress ([Details](https://travis-ci.org/PieceMeta/node-metakit/builds/440329631?utm_source=github_status&utm_medium=notification)). - ❌ **continuous-integration/appveyor/branch:** AppVeyor build failed ([Details](https://ci.appveyor.com/project/dasantonym/node-metakit/builds/19443708)).

---

Commits

The new version differs by 11 commits.

• 3e525eb v5.2.1
• 6d43b58 Delete bower.json
• 718ec5a v5.2.0
• 27dac46 Update API document
• d54f97e #107 sqrt of large number
• 373beed #63 round: negative argument
• 7aeb153 Merge pull request #101 from manix/patch-1
• b546c5e #grammarnazi
• e6847e9 Merge pull request #98 from opencollective/opencollective
• 953ea51 Added call to donate after npm install (optional)
• bdb8300 Added backers and sponsors on the README

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

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

[greenkeeper[bot]]

• The dependency big.js was updated from 5.2.1 to 5.2.2.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 1 commits.

• 01b3ce3 v5.2.2

See the full diff