Update eslint-plugin-import: 2.20.0 → 2.20.1 (patch)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ eslint-plugin-import (2.20.0 → 2.20.1) · Repo · Changelog

Release Notes

2.20.1 (from changelog)

Fixed

• export: Handle function overloading in *.d.ts (#1619, thanks @IvanGoncharov)
• no-absolute-path: fix a crash with invalid import syntax (#1616, thanks @ljharb)
• import/external-module-folders setting now correctly works with directories containing modules symlinked from node_modules (#1605, thanks @skozin)
• extensions: for invalid code where name does not exist, do not crash (#1613, thanks @ljharb)
• [extentions]: Fix scope regex (#1611, thanks @yordis)
• no-duplicates: allow duplicate imports if one is a namespace and the other not (#1612, thanks @sveyret)
• Add some missing rule meta schemas and types (#1620, thanks @bmish)
• named: for importing from a module which re-exports named exports from a node_modules module (#1569, #1447, thanks @redbugz, @kentcdodds)
• order: Fix alphabetize for mixed requires and imports ([#5625], thanks @wschurman)

Changed

• import/external-module-folders setting behavior is more strict now: it will only match complete path segments (#1605, thanks @skozin)
• [meta] fix "files" field to include/exclude the proper files (#1635, thanks @ljharb)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 23 commits:

• Bump to v2.20.1
• [Fix] `order`: Fix alphabetize for mixed requires and imports
• [Fix] `export`: Handle function overloading in `*.d.ts`
• [Fix] `no-absolute-path`: fix a crash with invalid import syntax
• [Fix] `named`: for importing from a module which re-exports named exports from a `node_modules` module
• [Tests] `named`: add failing test for #1446
• [meta] fix "files" field to include/exclude the proper files
• docs: fix a few spelling mistakes
• [Tests] set `eslint-plugin/consistent-output` lint rule to always require test case output assertions
• [meta] add missing changelog links
• [Tests] only run the linter once, not on every build
• [Tests] add eslint-plugin-eslint-plugin internally and fix violations
• [Docs]: Update Tidelift language to enterprise
• `no-duplicates`: allow duplicate if one is namespace and other not
• [Fix] `extensions`: Fix scope regex
• [Fix] `extensions`: for invalid code where `name` does not exist, do not crash
• [Fix] make 'import/order' work in a monorepo setup with scoped modules
• [Tests] enable a skipped test that's not failing anymore
• [meta] Merge duplicated `Added` section; fix link
• utils: v2.5.2
• utils: [Fix] Makes the loader resolution more tolerant
• utils: [fix] prefer `createRequire` if available
• [meta] resolvers/*: fix prepublish script

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)