An in-range update of p-throttle is breaking the build 🚨

[greenkeeper]

The devDependency p-throttle was updated from 2.0.0 to 2.1.0.

🚨 View failing branch.

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

p-throttle 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 failed (Details).

---

Release Notes for v2.1.0

• Improve performance and memory usage (#11) 842bd88

Commits

The new version differs by 4 commits.

• 82080a5 2.1.0
• 88952ba Meta tweaks
• 842bd88 Improve performance and memory usage (#11)
• dddafd5 Remove moot ESLint disable comment

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

[greenkeeper]

• The devDependency p-throttle was updated from 2.1.0 to 2.1.1.

Your tests are still failing with this version. Compare changes

Release Notes for v2.1.1

• Clear timeout after aborting pending executions (#14) 98b8506

v2.1.0...v2.1.1

Commits

The new version differs by 2 commits.

• a295884 2.1.1
• 98b8506 Clear timeout after aborting pending executions (#14)

See the full diff