Version Details and Security Vulnerabilities

📦

@typescript-eslint/eslint-plugin

8.18.1

Comparision Betweeen 8.18.1 and 8.18.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.64 MB

Version 8.18.1 Details

The @typescript-eslint/eslint-plugin has a new release, version 8.18.1, following closely on the heels of version 8.18.0. Both versions provide the core TypeScript linting rules for ESLint, enabling developers to enforce code quality and consistency in their TypeScript projects. While seemingly a minor version bump, 8.18.1 includes important updates. The key differences lie in the updated dependencies of internal packages like @typescript-eslint/utils, @typescript-eslint/type-utils, @typescript-eslint/visitor-keys, @typescript-eslint/scope-manager, and @typescript-eslint/rule-tester and @typescript-eslint/rule-schema-to-typescript-types which moved from version 8.18.0 to 8.18.1. These internal package updates may contain bug fixes, performance improvements, and potentially new features that trickle down into the overall plugin behavior. Developers should be aware to check for any breaking changes, even in patch updates of these internal packages although it's not very common. The unpacked size of the package has slightly increased, which could be related to new rules, improved documentation, or internal data structures. It's also important to note the peer dependencies remain the same ensuring compatibility with ESLint versions 8.57.0 and 9.0.0, TypeScript versions 4.8.4 up to but not including 5.8.0, and the associated @typescript-eslint/parser. For users of @typescript-eslint/eslint-plugin, upgrading to 8.18.1 is recommended to leverage the latest bug fixes and potential performance improvements in the internal utilities, while remaining compatible with their existing tooling. Review the release notes accompanying version 8.18.1 will provide a fine-grained summary of the impact from these 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.