Version Details and Security Vulnerabilities

📦

eslint-plugin-import

1.10.2

Comparision Betweeen 1.10.2 and 1.10.0

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

N/A

Unpacked Size

N/A

Version 1.10.2 Details

Eslint-plugin-import is a valuable tool for JavaScript developers seeking to improve code quality and maintainability through robust import statement handling. Comparing versions 1.10.2 and 1.10.0 reveals subtle yet important upgrades. Both versions share the same core dependencies, ensuring consistent functionality with packages like pkg-up, es6-map, and lodash.* for resolving package paths and handling ES6 features. The development dependencies also remain largely consistent, focusing on testing and build processes with tools like chai, mocha, gulp, and Babel presets.

The critical difference lies in the supported ESLint versions defined within peerDependencies. Version 1.10.0 explicitly supports ESLint version 2.x, whereas version 1.10.2 broadens this support to include ESLint 3.x as well. This is a significant improvement because it allows developers using newer ESLint versions to seamlessly integrate the plugin without compatibility issues. Developers upgrading to ESLint 3.x should prioritize version 1.10.2 to ensure smooth operation. Both versions employ the MIT license, providing developers the freedom to use, modify, and distribute the plugin. The package promises comprehensive import statement analysis, improving code clarity and reducing potential runtime errors. When choosing between the versions, consider your ESLint version. For ESLint 2.x, version 1.10.0 suffices, but for projects using ESLint 3.x, version 1.10.2 is the recommended option.

Security Vulnerabilities

This site is an independent open-source project and is not affiliated with, endorsed by, or sponsored by npm, Inc. or GitHub, Inc. The name “npm” is a registered trademark of npm, Inc., used here solely to describe compatibility and reference publicly available npm package data.