An in-range update of write-file-atomic is breaking the build 🚨

[greenkeeper]

The dependency write-file-atomic was updated from 2.4.2 to 2.4.3.

🚨 View failing branch.

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

write-file-atomic is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build is in progress (Details).
• ❌ continuous-integration/appveyor/branch: AppVeyor build failed (Details).

---

Commits

The new version differs by 5 commits.

• f3b025d 2.4.3
• cf86dff autopublish on version bump
• a6107b7 changelog for 2.4.3
• f8b1552 Ignore errors raised by fs.closeSync()
• e5c9adb Appease standard

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