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

[greenkeeper]

Version 4.7.0 of mock-fs was just published.

Branch	Build failing 🚨
Dependency	mock-fs
Current Version	4.6.0
Type	devDependency

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

mock-fs 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).
• ✅ coverage/coveralls: First build on greenkeeper/mock-fs-4.7.0 at 92.377% (Details).

---

Commits

The new version differs by 15 commits.

• 8f84cc7 4.7.0
• c463fde Log changes
• 7c224b0 Merge pull request #252 from tschaub/updates
• 5e68c29 Merge pull request #247 from tricoder42/patch-1
• f54a322 Merge pull request #249 from maxwellgerber/fix/buffer-copy
• 15df910 Remove dev dependency on minimatch
• b81c39b Merge pull request #251 from maxwellgerber/fix/dirent-patch
• 38ca5db binding.readdir can take anywhere from 2 to 4 arguments
• 29f82dc Add tests for reading and writing using Uint8Array
• a90b7ac docs: add note about snapshot testing
• 28d65a7 Remove redundant check
• 076fca8 Merge pull request #242 from maxwellgerber/patch/open-directory-error
• f8e4eb6 add tests
• e363112 Limit package contents
• b3e86cb Throw error when a directory is opened

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

[pierceray]

fixed by #24