Version Details and Security Vulnerabilities

📦

eslint-plugin-import

2.29.1

Comparision Betweeen 2.29.1 and 2.29.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

115

Unpacked Size

1.16 MB

1.15 MB

Version 2.29.1 Details

Eslint-plugin-import version 2.29.1 represents a minor upgrade over its predecessor, version 2.29.0, offering subtle yet potentially impactful refinements for developers leveraging ESLint to enforce import sanity within their JavaScript and TypeScript projects. The core functionality remains the same: ensuring consistent, correct, and well-structured import statements across your codebase.

One key difference lies in a dependency update: tsconfig-paths is bumped from version 3.14.2 to 3.15.0 in the newer version. This update likely addresses bug fixes or performance improvements within tsconfig-paths, which resolves TypeScript paths based on your tsconfig.json configuration. Developers using advanced path aliasing in their TypeScript projects may benefit from this enhancement.

In the devDependencies, markdownlint-cli is updated from 0.35.0 to 0.38.0 and chai is downgraded from 4.3.7 to 4.3.10. Notably, eslint-doc-generator sees an update from version 1.4.3 to 1.6.1 that may include changes on how documentation is generated. The unpacked size of the package as well changed, the newer version has a size of 1211116 against 1209560 of the previous one.

Both versions retain broad compatibility with ESLint versions 2 through 8, ensuring that developers with diverse project setups can adopt the plugin. The peer dependency on ESLint and the consistent set of core dependencies like debug, semver, and is-core-module highlight the plugin's stability and continued focus on providing reliable import validation. Choose version 2.29.1 for the latest, potentially more refined, tooling and dependency versions, especially if you rely on complex TypeScript path resolution or care about markdown linting.

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.