Version Details and Security Vulnerabilities

📦

@typescript-eslint/eslint-plugin

8.31.0

Comparision Betweeen 8.31.0 and 8.30.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

810

Unpacked Size

2.38 MB

Version 8.31.0 Details

Version 8.31.0 of @typescript-eslint/eslint-plugin introduces subtle but potentially impactful changes compared to version 8.30.1. For developers leveraging TypeScript with ESLint, understanding these nuances is crucial for a smooth upgrading process and optimized code analysis.

The core dependencies, @typescript-eslint/utils, @typescript-eslint/type-utils, @typescript-eslint/visitor-keys, and @typescript-eslint/scope-manager, have all been updated to version 8.31.0, ensuring better consistency and potentially incorporating bug fixes or performance improvements within the core utilities.

A notable shift in the development dependencies involves replacing jest with vitest for testing. Vitest is a performant alternative to jest and has similar syntax and functionalities. You may notice a smaller footprint and potentially faster test execution if you use this library for testing your code. This switch signals a commitment to modern testing practices. Also, cross-env and @jest/types (29.6.3) were removed and vitest (^3.1.1) and @vitest/coverage-v8 (^3.1.1) were added to the devDependencies. Additionally, @typescript-eslint/rule-tester and @typescript-eslint/rule-schema-to-typescript-types were updated to 8.31.0 indicating improvements or fixes in the rule testing infrastructure. The peerDependencies specifications remain identical, ensuring compatibility with existing ESLint and TypeScript setups. The release dates are also interesting because they are showing dates on the future, maybe it's a bug on the registry.

While file count is the same, the unpackedSize changed from 2494583 to 2495720. Developers should thoroughly test their ESLint configurations after upgrading to ensure compatibility and prevent unexpected rule behavior. Carefully examine the changelog and release notes for detailed information regarding rule updates and potential breaking changes.

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.