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

[greenkeeper]

The devDependency eslint-plugin-import was updated from 2.20.0 to 2.20.1.

🚨 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 23 commits.

• 45f0860 Bump to v2.20.1
• 5d00854 [Fix] order: Fix alphabetize for mixed requires and imports
• bbd166b [Fix] export: Handle function overloading in *.d.ts
• 4665ec5 [Fix] no-absolute-path: fix a crash with invalid import syntax
• 392c6b9 [Fix] named: for importing from a module which re-exports named exports from a node_modules module
• cc5bde5 [Tests] named: add failing test for #1446
• aff3a46 [meta] fix "files" field to include/exclude the proper files
• 986ba74 docs: fix a few spelling mistakes
• 6274d96 [Tests] set eslint-plugin/consistent-output lint rule to always require test case output assertions
• a4d301b [meta] add missing changelog links
• 2d42464 [Tests] only run the linter once, not on every build
• 26f232b [Tests] add eslint-plugin-eslint-plugin internally and fix violations
• 99647f1 [Docs]: Update Tidelift language to enterprise
• f84d457 no-duplicates: allow duplicate if one is namespace and other not
• 7e71b50 [Fix] extensions: Fix scope regex

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