Version Details and Security Vulnerabilities

📦

eslint-plugin-vitest

0.5.4

Comparision Betweeen 0.5.4 and 0.5.3

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

383.24 KB

382.08 KB

Version 0.5.4 Details

Eslint plugin vitest has released a new stable version 0.5.4, offering subtle but important improvements over the previous version 0.5.3. Both versions are designed to enhance the Vitest testing experience by providing ESLint rules tailored for Vitest code. Developers already using version 0.5.3 can upgrade to version 0.5.4 for incremental improvements.

A notable change lies in the dependencies. Version 0.5.4 updates @typescript-eslint/utils from version ^7.6.0 to ^7.7.1, aligning with the latest advancements in TypeScript ESLint support. This upgrade likely includes bug fixes and performance improvements within the core TypeScript ESLint infrastructure. The new version bumps to ^7.7.1 also @typescript-eslint/eslint-plugin, @typescript-eslint/parser and @typescript-eslint/rule-tester. It has a new version also @stylistic/eslint-plugin from ^1.7.0 to ^1.7.2

While the core functionality remains consistent, this dependency update ensures developers benefit from the most up-to-date linting capabilities. Both versions share the same peer dependencies, requiring "eslint": "^8.57.0 || ^9.0.0" and "vitest": "*", ensuring compatibility with a wide range of existing ESLint and Vitest setups. Developers can expect a smooth transition when upgrading, leveraging the updated TypeScript ESLint utilities for enhanced code quality and consistency within their Vitest testing suites. The unpacked size is slightly larger in the new version, with an increase of approximately 1KB (391249 vs 392441). This suggests minor additions or refinements within the core plugin logic.

Choosing between the versions depends on a developer's desire for the latest dependency updates and potential micro-optimizations.

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.