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

[greenkeeper]

The dependency babel-eslint was updated from 10.0.1 to 10.0.2.

🚨 View failing branch.

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

babel-eslint 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/appveyor/branch: AppVeyor build failed (Details).
• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
• ✅ coverage/coveralls: First build on greenkeeper/babel-eslint-10.0.2 at 100.0% (Details).

---

Release Notes for v10.0.2

Fixes #772

Commits

The new version differs by 2 commits.

• 48f6d78 10.0.2
• 0241b48 removed unused file reference (#773)

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

[greenkeeper]

• The dependency babel-eslint was updated from 10.0.2 to 10.0.3.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• 183d13e 10.0.3
• 354953d fix: require eslint dependencies from eslint base (#794)

See the full diff

[greenkeeper]

• The dependency babel-eslint was updated from 10.0.3 to 10.1.0.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 2 commits.

• 4bd049e 10.1.0
• 2c754a8 Update Babel to ^7.7.0 and enable Flow enums parsing (#812)

See the full diff