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

[greenkeeper]

The devDependency jsverify was updated from 0.8.3 to 0.8.4.

🚨 View failing branch.

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

jsverify 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).

---

Commits

The new version differs by 25 commits.

• 48ba3e5 Release 0.8.4
• 5d40ead Merge pull request #277 from jsverify/updates-2018-10-31
• 85384bf Disable node 6 on travis
• b8338f4 grammar fix in arbitrary.smap documentation
• 5325c1d Duplicate i.e. i.e.
• f2a35e9 Update .travis.yml
• 005f113 Update 2018-10-31
• 28be14f Merge pull request #270 from SydneyUniLibrary-Jim/issue-242
• 261b45d Fixed TypeScript bindings for either.
• b1f63f5 Merge pull request #267 from jsverify/travis-node-ver
• f99de9a Adjust node versions
• e018582 Update ts-node
• 0d392dd Merge pull request #247 from xtianjohns/jasmine-helpers
• 6f96085 Generate readme
• 6e0b0ba Remove outdated Jasmine reference in readme

There are 25 commits in total.

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