Version Details and Security Vulnerabilities

📦

eslint-plugin-import

0.10.0

Comparision Betweeen 0.10.0 and 0.9.1

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.10.0 Details

eslint-plugin-import version 0.10.0 introduces several key updates compared to the earlier stable version 0.9.1, impacting developers utilizing the plugin to enforce import sanity in their JavaScript projects. Most notably, version 0.10.0 features an updated babylon dependency, moving to ^6.1.2 from 6.0.18, potentially incorporating enhancements and bug fixes within the Babylon parser. Simultaneously, babel-eslint is updated to ^4.1.4 compared to 4.1.3.

A significant change can be seen in the peer dependencies, the newer version requires eslint version to be ">=1.4.0" which is different from the eslint version required by the older version, ">=0.16.0". This change indicates adjustments in compatibility or new features leveraging newer ESLint versions. The devDependencies also reveal an important removal, acorn-to-esprima no longer listed, implying that it is no longer necessary for development or testing processes.

For developers, upgrading to version 0.10.0 can benefit projects through enhanced parser compatibility with ES6+ syntax (via Babylon), potentially resolving parsing issues encountered in version 0.9.1. The upgrade to newer eslint versions enable using more advanced linting rules and best practices and remove dependency. It's advisable for developers to review their ESLint configurations and test their projects thoroughly after upgrading to ensure full compatibility and leverage the improvements introduced in this release.

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.