Version Details and Security Vulnerabilities

📦

@typescript-eslint/eslint-plugin

8.16.0

Comparision Betweeen 8.16.0 and 8.15.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

552

Unpacked Size

2.63 MB

2.61 MB

Version 8.16.0 Details

The @typescript-eslint/eslint-plugin package, a cornerstone for TypeScript linting within ESLint, has released version 8.16.0, building upon the solid foundation of its predecessor, version 8.15.0. Both versions maintain the core functionality of providing ESLint rules specifically tailored for TypeScript code, ensuring code quality, consistency, and adherence to best practices.

Developers upgrading to 8.16.0 will find subtle, but important updates in its internal dependencies. Key dependency upgrades can be found in @typescript-eslint/utils, @typescript-eslint/type-utils, @typescript-eslint/visitor-keys, @typescript-eslint/scope-manager, @typescript-eslint/rule-tester and @typescript-eslint/rule-schema-to-typescript-types, all moving from version 8.15.0 to 8.16.0. These updates likely incorporate bug fixes, performance enhancements, and potentially new features within the underlying utilities that directly influence the behavior of the ESLint rules. While the surface-level changes might not be immediately apparent to the average user, these internal improvements enhance the stability and reliability of the linting process.

The dist metadata shows an increase in unpackedSize, suggesting the updates add new features without removing old code. The library enables developers to enforce coding standards, detect potential errors, and improve the overall maintainability of TypeScript projects, seamlessly integrating with existing ESLint workflows. Peer dependencies like eslint and @typescript-eslint/parser remain unchanged, ensuring compatibility with existing project setups requiring ESLint versions ^8.57.0 || ^9.0.0 and parser versions ^8.0.0 || ^8.0.0-alpha.0 respectively.

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.