An in-range update of find-cache-dir is breaking the build 🚨

[greenkeeper]

The devDependency find-cache-dir was updated from 3.1.0 to 3.2.0.

🚨 View failing branch.

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

find-cache-dir 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

• ✅ codecov/project: 85.23% remains the same compared to a855d74 (Details).
• ✅ lint (windows-latest): null
• ❌ Travis CI - Branch: The build failed.
• ✅ lint (macos-latest): null
• ✅ lint (ubuntu-latest): null
• ✅ test-unit (windows-latest): null
• ✅ test-unit (macos-latest): null
• ✅ test-unit (ubuntu-latest): null

---

Release Notes for v3.2.0

• Tolerate lack of node_modules when checking if directory is writable (#20) a2679d9

v3.1.0...v3.2.0

Commits

The new version differs by 4 commits.

• c432cb4 3.2.0
• a0c487f Meta tweaks
• a2679d9 Tolerate lack of node_modules when checking if directory is writable (#20)
• d3c64a7 Add Storybook to list of adopters (#21)

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