Version Details and Security Vulnerabilities

📦

eslint-plugin-import

0.3.9

Comparision Betweeen 0.3.9 and 0.3.8

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

eslint-plugin-import version 0.3.9 is a minor release over the previous stable version 0.3.8, both designed to bring sanity to ES modules and CommonJS import statements within ESLint. Examining the package metadata reveals only subtle distinctions. The core functionality, indicated by the unchanged dependencies like espree, es6-map, resolve, and estraverse, remains consistent. This suggests the underlying parsing and resolution logic for import statements is stable.

Similarly, development dependencies used for testing and building, like chai, mocha, eslint, and eslint-tester, are consistent, indicating no major shifts in the testing or build process happened as part of this patch. The peer dependency on eslint itself remains at ">=0.16.0", confirming compatibility with existing ESLint setups.

The most notable difference is the releaseDate. Version 0.3.9 was published just a few minutes after 0.3.8, which is an important detail. Given the identical dependency versions, this suggests the update might contain very minor bug fixes, documentation updates, or adjustments to the publishing process and not some major feature or deep change. Developers considering upgrading from 0.3.8 can likely do so with minimal risk of compatibility issues. However, consulting the changelog (available on the GitHub repository) is always recommended to understand the precise nature of the changes and any potential impact on their specific codebase. If you are experiencing some obscure edge case with version 0.3.8, there is a small chance it was fixed in this release, but for most users, the changes should be totally transparent.

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.