eslint-plugin-import
2.32.0 · 20 Jun 2025MIT84.5M / weekRepositorynpmAtom feed
1.16.0 is the newest release of 1.x.
In short
1 breaking2 changed
- Breaking
eslint-config-import is no longer supported.
Release note
import/no-deprecated: WIP rule to let you know at lint time if you're using deprecated functions, constants, classes, or modules.
From the beta 1.0 release notes:
Update, verified to work with ESLint 2.0.
"Breaking" changes from 0.13.0:
no longer needs/refers to import/parser or import/parse-options. instead, ESLint provided the configured parser + options to the rules, and they use that to parse dependencies.
Shouldn't hurt to leave it there, and I suspect 99.999% of installs have import/parser === parser.
This also means the plugin uses espree instead of babylon if no parser is configured. Wouldn't expect this to hurt in general, but it is a potentially breaking difference.
eslint-config-import is no longer supported. Instead, use the shared configs directly exported by the plugin. See the README for details.
Nothing groundbreaking, but import/parser has been a thorny issue for the whole life of the plugin, and I'm glad to finally be rid of it. :sweat_smile:
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.