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

[greenkeeper]

The devDependency proxyquire was updated from 2.1.0 to 2.1.1.

🚨 View failing branch.

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

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

---

Commits

The new version differs by 6 commits.

• 5b88b07 2.1.1
• 3905975 Update dependencies (#243)
• 3ca62af funding: adding github funding spec
• 12606d1 README.md: Fix typo (#241)
• 3da0603 Add file path reference to readme (#237)
• cb725be readme: fix simple-get example

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.1.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 proxyquire was updated from 2.1.1 to 2.1.2.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• cc9cdb6 2.1.2
• 0297d28 fix: allow non-existent stub path when @noCallThru is set at stub level (#245)

See the full diff

[greenkeeper]

• The devDependency proxyquire was updated from 2.1.2 to 2.1.3.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• aaae296 2.1.3
• 6a01bc1 fix: throw correct error when simulating MODULE_NOT_FOUND (#246)

See the full diff