Version Details and Security Vulnerabilities

📦

eslint-plugin-vitest

0.3.22

Comparision Betweeen 0.3.22 and 0.3.21

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

349.93 KB

351.71 KB

Version 0.3.22 Details

Eslint-plugin-vitest has a new release, version 0.3.22, building upon the previous stable version 0.3.21. This update brings notable changes primarily in dependency updates. Specifically, @typescript-eslint/utils has been bumped from version 6.20.0 to ^6.21.0. This is synchronized with upgrades to @typescript-eslint/eslint-plugin and @typescript-eslint/rule-tester which also move from 6.20.0 to ^6.21.0, likely introducing new features, bug fixes, and performance improvements related to TypeScript linting and rule testing within the vitest environment. For developers utilizing TypeScript and vitest, these dependency updates are significant, potentially resolving compatibility issues or unlocking enhanced analysis capabilities for their test suites.

A subtle but important change is an update on the eslint-plugin-vitest's version used as a dev dependency for itself, which increases from 0.3.20 to ^0.3.21, demonstrating a gradual iterative refinement of the plugin and its internal testing mechanisms. While the peer dependencies on eslint (">=8.0.0") and vitest ("*") remain consistent, ensuring broad compatibility, the updated dependencies suggest a closer alignment with the latest TypeScript ecosystem tooling. The unpacked size of the package has slightly decreased, meaning the new version it's a bit lighter than the older one. Version 0.3.22 was released on February 6th, 2024, a week after version 0.3.21, released on January 30th, 2024.

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.