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

[greenkeeper[bot]]

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 2.0.1 of proxyquire was just published.

Branch	Build failing 🚨
Dependency	proxyquire
Current Version	2.0.0
Type	devDependency

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/appveyor/branch** Waiting for AppVeyor build to complete [Details](https://ci.appveyor.com/project/gucong3000/gulp-reporter/build/1293) - ❌ **ci/circleci** Your tests failed on CircleCI [Details](https://circleci.com/gh/gucong3000/gulp-reporter/476?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/gucong3000/gulp-reporter/builds/355613536?utm_source=github_status&utm_medium=notification)

---

Commits

The new version differs by 3 commits.

• 58a6321 2.0.1
• 851baaa Clean up proxyquired module after restoring cache
• d3a155d Update to resolve@1.5 (#194)

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your Greenkeeper Bot :palm_tree:

[greenkeeper[bot]]

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.