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

[greenkeeper]

The dependency deasync was updated from 0.1.15 to 0.1.16.

🚨 View failing branch.

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

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

---

Commits

The new version differs by 2 commits.

• d6b7e51 node v13
• ff6edc8 Update package-lock.json

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

[greenkeeper]

• The dependency deasync was updated from 0.1.16 to 0.1.17.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• ec9b879 Use current event loop instead of default
• 5f55000 Create FUNDING.yml

See the full diff

[greenkeeper]

• The dependency deasync was updated from 0.1.17 to 0.1.18.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by commits.

See the full diff