Skip to content
This repository was archived by the owner on Feb 2, 2021. It is now read-only.

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

Closed
greenkeeper bot opened this issue Aug 12, 2019 · 2 comments
Closed

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

greenkeeper bot opened this issue Aug 12, 2019 · 2 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Aug 12, 2019

The devDependency proxyquire was updated from 2.1.2 to 2.1.3.

🚨 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 2 commits.

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

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
Copy link
Contributor Author

greenkeeper bot commented Aug 12, 2019

After pinning to 2.1.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

@helio-frota
Copy link
Contributor

Using the latest, closing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant