Version Details and Security Vulnerabilities

📦

eslint-plugin-import

0.7.0

Comparision Betweeen 0.7.0 and 0.6.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 0.7.0 Details

Eslint-plugin-import version 0.7.0 builds upon the solid foundation of version 0.6.0, offering developers a refined experience in enforcing import sanity within their JavaScript projects. Both versions share the core dependency structure, relying on packages like espree for parsing, es6-map and es6-set for ES6 data structures, resolve for module resolution, and array.prototype.find for array manipulation. Development dependencies remain consistent, utilizing tools like chai and mocha for testing, eslint for linting, istanbul for code coverage, eslint-tester for ESLint rule testing, and object-assign for object manipulation. The peer dependency on eslint remains at ">=0.16.0" ensuring compatibility with relevant ESLint versions.

The key difference lies in the release date, with version 0.7.0 being published on July 16, 2015, shortly after version 0.6.0 which was released on July 15, 2015. This suggests that version 0.7.0 likely includes bug fixes or minor enhancements implemented based on immediate feedback or issues discovered after the 0.6.0 release. While the package metadata doesn't explicitly detail the changes, developers should consider version 0.7.0 a potentially more stable and refined option due to its later release. For developers actively using eslint-plugin-import, upgrading to version 0.7.0 is recommended to benefit from any potential fixes or improvements. Both versions are MIT licensed, authored by Ben Mosher, and available for use in any project.

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.