Version Details and Security Vulnerabilities

📦

eslint-plugin-import

0.7.8

Comparision Betweeen 0.7.8 and 0.7.7

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

ESLint Plugin Import, a tool designed to bring sanity to JavaScript imports, saw a minor version bump from 0.7.7 to 0.7.8 in August 2015. This update primarily involved changes in the development dependencies, reflecting adjustments in the tooling used for testing and building the plugin. Notably, the eslint dev dependency was updated from ">=0.16.0" to "^1.1.0" signifying a shift towards compatibility with ESLint version 1.1.0 and newer, potentially unlocking new linting features or rule configurations. Also, the eslint-tester dev dependency present in version 0.7.7 was removed in version 0.7.8.

For developers using the plugin, the core functionality related to import linting remained largely consistent between the two versions. Both versions depend on espree, resolve, and babel-runtime for parsing and resolving modules, ensuring continued compatibility with existing codebases. Similarly, the peer dependency on ESLint itself, specified as ">=0.16.0" in both versions, ensures that the plugin integrates smoothly with various ESLint installations.

The MIT license continues to provide developers with the freedom to use, modify, and distribute the plugin. While the 0.7.8 release might not have introduced significant user-facing changes, It's always recommended to stay updated with the latest versions for potential bug fixes, performance improvements, and enhanced compatibility with the broader JavaScript ecosystem especially with projects using ESLint.

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.