Eslint-plugin-import, a tool designed to bring sanity to JavaScript imports within your ESLint workflow, saw a notable update with the release of version 0.11.0 following version 0.10.1. Both versions maintain the core promise of linting import statements for better code quality and maintainability, but the 0.11.0 release introduces changes relevant to developers seeking robust import handling.
A key difference lies in the dependency management. Version 0.11.0 replaces the direct dependency on resolve found in 0.10.1 with eslint-import-resolver-node. This signifies a shift towards a more modular and configurable approach to resolving import paths. Instead of relying on a fixed resolution algorithm, developers can now utilize resolvers like eslint-import-resolver-node to customize how ESLint finds imported modules, enhancing compatibility with diverse project setups, including those using Node.js-style module resolution. Version 0.11.0 also adds eslint-import-resolver-webpack as dev dependency allowing to resolve webpack modules.
Developers upgrading to 0.11.0 should note the removal of resolve as a direct dependency and consider the implications for their ESLint configuration. The introduction of resolver dependencies enables more granular control over import resolution, a boon for complex projects, while retaining familiar peer dependencies such as ESLint itself. This change promotes flexibility and integration with various module resolution strategies commonly employed in modern JavaScript development.
The are not vulnerabilities for the version 0.11.0 of the package eslint-plugin-import