An in-range update of fetch-mock is breaking the build 🚨

[greenkeeper]

The devDependency fetch-mock was updated from 8.2.1 to 8.3.0.

🚨 View failing branch.

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

fetch-mock 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

• ❌ Travis CI - Branch: The build failed.

---

Commits

The new version differs by 22 commits.

• 6290ca4 Merge pull request #491 from wheresrhys/matcher-object
• e7e6503 reorg
• a613d8f update types
• 110e001 improve exaples
• a2f75f6 better documentation of complex matcher patterns
• 84c95a4 documentation update
• 3b239cc Merge pull request #492 from wheresrhys/refactor-for-obj-matcher
• 125a178 tidy
• 3294162 fixed all tests
• 815eb1b begininng to refactor tests
• a6a3c80 fix test ad lint
• befeef4 remove logs
• fbadda5 converted most behaviour to separate url from other matchers
• 7680d9e tests for a matcher object
• 96a76f2 Update resetHistory.md

There are 22 commits in total.

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

[gr2m]

See wheresrhys/fetch-mock#493

[gr2m]

Should be fixed in 8.3.1 via wheresrhys/fetch-mock#494

[github-actions]

🎉 This issue has been resolved in version 2.4.3 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀