Version Details and Security Vulnerabilities

📦

eslint-plugin-import

1.9.2

Comparision Betweeen 1.9.2 and 1.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 1.9.2 Details

Eslint-plugin-import version 1.9.2 is a minor update to version 1.9.1 of the popular ESLint plugin designed to enhance JavaScript code quality by enforcing import-related best practices. Both versions focus on bringing sanity to JavaScript module imports, helping developers write cleaner and more maintainable code. A key feature shared by both versions is their set of rules to prevent common import errors, such as importing non-existent modules, misspellings, and circular dependencies.

Examining the dependency lists reveals that the core dependencies haven't changed between versions. Both versions rely on the same core libraries such as pkg-up, es6-map, doctrine, and various lodash utilities. Similarly, their development dependencies including tools like chai, glob, gulp, and testing frameworks such as mocha remain consistent. This means the underlying mechanics for linting import statements haven't received major overhauls.

The most notable difference between the two versions is the release date, with version 1.9.2 being released on June 21, 2016, five days after version 1.9.1. This suggests that version 1.9.2 likely includes bug fixes. Developers already using 1.9.1 should upgrade, because it contains small fixes and general stability. For new users, start with 1.9.2 to benefit from any immediate improvements upon the previous version. Both versions share features and aim to enhance the process of managing and enforcing clean imports in JavaScript projects.

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.