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

## Version **8.1.0** of [babel-eslint](https://github.com/babel/babel-eslint) was just published.

Branch


Build failing 🚨




Dependency


babel-eslint




Current Version


8.0.3




Type


devDependency

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

babel-eslint 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

- ❌ **ci/circleci** Your tests failed on CircleCI [Details](https://circleci.com/gh/iansinnott/react-static-webpack-plugin/463?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)

---

Release Notes
v8.1.0

Use ESLint's API to customize scope analysis and avoid monkeypatching: #542

Commits

The new version differs by 3 commits.

• 893a5e3 8.1.0


• bba9d00 Re-add parseNoPatch function (accidentally removed) (#557)


• dbc6546 Use new scopeManager/visitorKeys APIs (#542)

See the full diff

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:

Beginne mit der Prüfung des babel-eslint-Updates von 8.0.3 auf 8.1.0 und des im Issue verknüpften fehlgeschlagenen ci/circleci-Laufs. Ermittle, warum der Build nach dem Update innerhalb des Versionsbereichs fehlschlägt, und verifiziere anschließend, dass der Projekt-Build und die Tests mit einer geeigneten Abhängigkeitsänderung erfolgreich sind.

Vom Indexierungsmodell aus dem Issue-Text verfasst.