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

[greenkeeper[bot]]

The devDependency eslint-config-precure was updated from 2.7.0 to 2.8.0.

🚨 View failing branch.

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

eslint-config-precure 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/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/ming-codes/babel-plugin-pegjs-inline-precompile/builds/431172272?utm_source=github_status&utm_medium=notification)).

---

Commits

The new version differs by 3 commits.

• 4a5f9e0 chore(npm): use np
• 3a11679 feat(rule): Fix parserOptions for ESLint v5.x.x
• e13a3db chore(npm): update

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 Bot :palm_tree:

[greenkeeper[bot]]

After pinning to 2.7.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper[bot]]

• The devDependency eslint-config-precure was updated from 2.8.0 to 2.8.1.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 1 commits.

• 41c5d17 chore(npm): yarn

See the full diff