An in-range update of eslint-watch is breaking the build 🚨

[greenkeeper]

Version 3.1.1 of eslint-watch just got published.

Branch	Build failing 🚨
Dependency	eslint-watch
Current Version	3.1.0
Type	devDependency

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

As eslint-watch is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ✅ continuous-integration/travis-ci/push The Travis CI build passed Details
• ❌ coverage/coveralls First build on greenkeeper/eslint-watch-3.1.1 at 84.456% Details

---

Release Notes

v3.1.1 - Misc Fixes Eslint 4.0.0 support

Fixes

• Grey text fix (#118)
• Key undefined fix (#116)

Misc

• Dependencies Update (#117)

Commits

The new version differs by 4 commits.

• 049a924 3.1.1
• a36a1ed Check if key is defined (#116)
• a8924bd Make gray text readable on Solarized Dark theme (#118)
• 7f8a3f6 Updating dependencies and eslint restrictions (#117)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

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.

[greenkeeper]

Version 3.1.2 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 3 commits.

• 1273b5c 3.1.2
• 1e92ad8 updating gif
• 304bdfc Check if key is defined when logging (#121)

See the full diff