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

[greenkeeper]

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

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

🚨 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

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Commits

The new version differs by 14 commits.

• 71ca88f Bump to v2.20.2
• a618f88 [Tests] pin esquery, due to breaking change in a minor version
• 9c5899e utils: v2.6.0
• efb5f07 [Tests] use babel instead of NODE_PATH
• 1a3a128 [Fix] first: Add a way to disable absolute-first explicitly
• efd6be1 [Fix] no-unused-modules: handle export { default } from syntax
• adbced7 utils: [New] Print more helpful info if parsing fails
• b6242b0 [fix] no-duplicates: fix fixer on cases with default import
• 41aaa18 resolvers/node: [New] add .node extension
• 12971f5 [Fix] order: recognize ".." as a "parent" path
• 47f912e [Fix] order: fix isExternalModule detection on windows
• 8905007 [Tests] appveyor: on node 8-12, use npm 6.10.3
• 2beec94 [meta] use in-publish in prepublish
• 1fbef73 [meta] fix changelog link

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