eslint-plugin-import
2.32.0 · 20 Jun 2025MIT84.5M / weekRepositorynpmAtom feed
Upgrading eslint-plugin-import From 1.16.0 to 2.0.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 4
- changes to make
- 0
- advisories fixed
- 5
- new
- 1
- fix
Before you upgrade
Tick each one off as you go- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
- Breaking2.0.0
Release by release
- Breaking
Add option
newlines-between: "ignore"to [order] ([#519], thanks [@sompylasar]) - Breaking
[
import/extensionssetting] defaults to['.js']. ([#306], thanks [@benmosher]) - Breaking
[
import/ignoresetting] defaults to nothing, and ambiguous modules are ignored natively. This means importing from CommonJS modules will no longer be reported by [default], [named], or [namespace], regardless ofimport/ignore. ([#270], thanks [@benmosher]) - Breaking
[
newline-after-import]: Removed need for an empty line after an inlinerequirecall ([#570], thanks [@sindresorhus])
- Breaking
2 other lines we could not sort, mostly version bumps
- 2.0.0
imports-firstis renamed to [first].imports-firstalias will continue to exist, but may be removed in a future major release. - 2.0.0
Case-sensitivity: Now specifically (and optionally) reported by [
no-unresolved]. Other rules will ignore case-mismatches on paths on case-insensitive filesystems.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.