Version Details and Security Vulnerabilities

📦

eslint-plugin-import

1.10.3

Comparision Betweeen 1.10.3 and 1.10.2

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

eslint-plugin-import version 1.10.3 is a minor update to the popular ESLint plugin that helps enforce import best practices. Released on July 12, 2016, roughly a week after version 1.10.2, the upgrade includes a change in its dependencies. Specifically, the dependency es6-symbol that was present in version 1.10.2 has been removed. Furthermore, several development dependencies have either been removed, modified, or added. Version 1.10.3 removes gulp-mocha and gulp-changed. It also upgrades eslint from 3.x to 2.x. Besides that, it adds babel-plugin-istanbul and upgrades babel-register. These modifications suggest possible refinements in the plugin's testing, code coverage, or build processes.

For developers, this means that upgrading from 1.10.2 might require adjustments to your local development environment, especially if you rely on the specific removed development dependencies in your workflow. Both versions maintain peer dependency compatibility with ESLint versions 2.x through 3.x, offering flexibility for integration into existing projects. When choosing between the two, consider whether the removal of es6-symbol or the development dependency modifications impact your project's stability or development pipeline. Checking the changelog associated with this specific version jump is highly recommended for a complete picture of the bug fixes, performance improvements, and new features (if any) included in this relatively small 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.