An in-range update of @ljharb/eslint-config is breaking the build 🚨

[greenkeeper]

The devDependency @ljharb/eslint-config was updated from 13.0.0 to 13.1.0.

🚨 View failing branch.

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

@ljharb/eslint-config 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).

---

Commits

The new version differs by 5 commits.

• 2dd67e5 v13.1.0
• 34a402a [Minor] update config and require eslint v5.11
• fd1f310 [Dev Deps] update eslint, replace, safe-publish-latest, semver
• 2d1a944 [Tests] use npm audit instead of nsp
• a02c14b [Tests] up to node v11.6, v10.15, v8.15, v6.16

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

[greenkeeper]

• The devDependency @ljharb/eslint-config was updated from 13.1.0 to 13.1.1.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 3 commits.

• 9254811 v13.1.1
• 86527f0 [Deps] update eslint
• 7f95eac [patch] disable func-names; too noisy

See the full diff

[ljharb]

Fixed.