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

[Greenkeeper]

The devDependency chalk was updated from 2.4.1 to 2.4.2.

🚨 View failing branch.

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

chalk 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/appveyor/branch: Waiting for AppVeyor build to complete (Details).
• ✅ continuous-integration/travis-ci/push: The Travis CI build passed (Details).
• ❌ coverage/coveralls: First build on greenkeeper/chalk-2.4.2 at 88.015% (Details).

---

Release Notes for v2.4.2

• Strict mode in Flow definition (#309) f95d9ec

---

This release is done from the v2-release branch, as master branch targets the work-in-progress v3 release.

Commits

The new version differs by 2 commits.

• 9776a2a 2.4.2
• f95d9ec Strict mode in Flow definition (#309)

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