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

[greenkeeper]

The dependency big-integer was updated from 1.6.42 to 1.6.43.

🚨 View failing branch.

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

big-integer 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 could not complete due to an error (Details).

---

Commits

The new version differs by 3 commits.

• 2e06193 update npm
• 48622b8 Merge pull request #176 from pashinin/master
• 2077aea Add "alphabet" argument to toString()

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

[greenkeeper]

• The dependency big-integer was updated from 1.6.43 to 1.6.44.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

• 825bdbd minify, update npm
• bfd7b32 Merge pull request #185 from pepijno/feature/modpow-negative-exponents
• c0f80af Changed modPow to also handle negative exponents by using the

See the full diff