Version Details and Security Vulnerabilities

📦

eslint-plugin-import

2.19.0

Comparision Betweeen 2.19.0 and 2.18.2

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

714.99 KB

659.88 KB

Version 2.19.0 Details

Eslint-plugin-import offers static analysis for ES2015+ imports, bolstering code quality and preventing common pitfalls. Version 2.19.0 introduces several notable changes compared to version 2.18.2, making it an appealing upgrade. One key difference lies in its updated dependencies. Notably, "resolve" is bumped from version 1.11.0 to 1.12.0, potentially bringing bug fixes and performance improvements in module resolution. Additionally, eslint-module-utils moves from version 2.4.0 to 2.4.1 providing possibly new utilities or enhancements to existing ones for ESLint module handling. Furthermore, array.prototype.flat is introduced as a new dependency at version 1.2.1, suggesting a potential expansion in the plugin's capabilities around array manipulation within import statements.

Beyond dependency updates, the newer version showcases adjustments in the development environment. While most devDependencies remain consistent, "rimraf" sees an upgrade from version 2.6.3 to 2.7.1. "semver" jumps from 6.0.0 to 6.3.0, reflecting enhanced semantic version handling during development and testing. The increase in fileCount from 62 to 63 and unpackedSize hints at added functionalities or expanded test coverage in version 2.19.0 improving the overall stability and reliability of the plugin. Finally, the releaseDate differs significantly, showing that 2.19.0 has incorporated a whole semester worth of updates since the earlier 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.