Version Details and Security Vulnerabilities

📦

eslint-plugin-jest

29.0.0

Comparision Betweeen 29.0.0 and 28.14.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

140

Unpacked Size

347.23 KB

349.05 KB

Version 29.0.0 Details

Eslint-plugin-jest provides ESLint rules tailored for Jest testing, helping developers enforce best practices and catch potential errors in their Jest test suites. Comparing versions 29.0.0 and 28.14.0 reveals subtle but important shifts in dependencies and peer dependencies, influencing compatibility and potentially requiring adjustments when upgrading.

Version 29.0.0 specifies "@typescript-eslint/utils":"^8.0.0" in dependencies, a narrower range than version 28.14.0 which allows "^6.0.0 || ^7.0.0 || ^8.0.0". This may impact TypeScript projects using older versions of @typescript-eslint. For peer dependencies, version 29.0.0 requires "@typescript-eslint/eslint-plugin":"^8.0.0" unlike version 28.14.0 where the dependency was "@typescript-eslint/eslint-plugin":"^6.0.0 || ^7.0.0 || ^8.0.0", making the new version tighter on peer dependencies version. Notably, the eslint peer dependency in version 29.0.0 is defined as "^8.57.0 || ^9.0.0", locking in a specific minimum ESLint version, different than the broader "^7.0.0 || ^8.0.0 || ^9.0.0" of 28.14.0. Differently version 28.14.0 has "@tsconfig/node16":"^16.0.0" and "strip-ansi":"^6.0.0" in the devDependencies, whereas version 29.0.0 has "@tsconfig/node20":"^20.0.0". These changes suggest a move towards more recent tooling.

Developers should carefully review these dependency changes as upgrading from 28.14.0 to 29.0.0 may necessitate updates to their project's ESLint, TypeScript, and related configurations to ensure compatibility and avoid unexpected issues. The releaseDate of the two versions is in the future, which is not right.

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.