Version Details and Security Vulnerabilities

📦

@typescript-eslint/eslint-plugin

5.30.6

Comparision Betweeen 5.30.6 and 5.30.5

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

454

Unpacked Size

2.19 MB

Version 5.30.6 Details

Version 5.30.6 of @typescript-eslint/eslint-plugin, a TypeScript plugin for ESLint, was released on July 11, 2022, succeeding version 5.30.5 which was released a week earlier on July 4, 2022. While both versions share the same core functionality of providing ESLint rules for TypeScript code, enabling developers to enforce consistent code style and best practices, a closer look reveals subtle yet important distinctions beneath the surface.

The primary difference lies in the dependency versions within the @typescript-eslint ecosystem. Version 5.30.6 boasts updated versions of @typescript-eslint/utils, @typescript-eslint/type-utils, and @typescript-eslint/scope-manager all bumped to 5.30.6 to keep parity. Version 5.30.5 relied on version 5.30.5 of these core packages. This synchronization within the @typescript-eslint suite ensures optimal compatibility and leverages any bug fixes or performance enhancements introduced in those specific sub-packages between the two releases.

Developers considering an upgrade should be mindful of these dependency changes. While seemingly minor, updates across the @typescript-eslint suite often address nuanced edge cases and subtle type-checking issues. Staying current ensures your linting process benefits from the latest refinements, leading to more accurate and reliable code analysis. The core dependencies like debug, ignore, semver remains the same. Both versions maintain identical development dependencies, peer dependencies, license, repository details, funding information, file count and unpacked size, ensuring a smooth transition for upgrading developers. The most interesting part of using this library is to enforce a coding style along your code with auto-fixes and make sure to catch typescript errors.

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.