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

[Greenkeeper]

The devDependency eslint-plugin-import was updated from 2.17.2 to 2.17.3.

🚨 View failing branch.

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

eslint-plugin-import 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

• ❌ Travis CI - Branch: The build errored.

---

Commits

The new version differs by 25 commits.

• cf5573b Bump to v2.17.3
• caae65c [Tests] eslint 2 does not have linter.version
• 557a3e2 [Deps] update resolve
• 17beb33 Merge pull request #1356 from christophercurrie/typescript-declare
• c8ac7ff [Docs] Document env option for eslint-import-resolver-webpack
• c09c0ce Issue #1258 (docs)
• 753c9db [refactor] fix eslint 6 compat by fixing imports
• b52bf3e PR feedback
• 7aa13d1 PR feedback
• f66e064 Remove log messages
• d1e4455 Verbose variable names
• 67b1e95 Support older typescript parsers
• 288cedf Make groups non-capturing.
• aa290bb Improve support for Typescript declare structures
• 1edbbd0 [Fix] no-common-js: Also throw an error when assigning

There are 25 commits in total.

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