An in-range update of chokidar is breaking the build 🚨

[greenkeeper]

The devDependency chokidar 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.

chokidar 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

• ❌ triggered-by-commit: * build - Failed

---

Commits

The new version differs by 4 commits.

• 1ea6388 Release 2.1.3.
• d60635f Update README.
• a8f64aa bump upath version to fix problems related with yarn (#808)
• 8f56261 A better workaround for atomic writes (#791)

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]

• The devDependency chokidar was updated from 2.1.3 to 2.1.4.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by 2 commits.

• fc243cd Release 2.1.4.
• 4954842 add typing to event listeners (#811)

See the full diff

[greenkeeper]

After pinning to 2.1.2 your tests are passing again. Downgrade this dependency 📌.

[greenkeeper]

• The devDependency chokidar was updated from 2.1.4 to 2.1.5.

Your tests are passing again with this update. Explicitly upgrade to this version 🚀

Commits

The new version differs by 4 commits.

• 3595b42 Release 2.1.5.
• b79120b Revert "A better workaround for atomic writes (#791)"
• fc243cd Release 2.1.4.
• 4954842 add typing to event listeners (#811)

See the full diff