Version Details and Security Vulnerabilities

📦

@typescript-eslint/parser

5.30.5

Comparision Betweeen 5.30.5 and 5.30.4

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

28.54 KB

Version 5.30.5 Details

Version 5.30.5 of @typescript-eslint/parser, a vital tool for ESLint integration in TypeScript projects, represents a subtle but potentially important update over its predecessor, version 5.30.4. Both versions share the same core functionality, providing a custom parser that allows ESLint to understand and analyze TypeScript code effectively. This allows developers to catch potential errors and enforce coding standards within their TypeScript projects seamlessly.

Key dependencies like debug, @typescript-eslint/types, @typescript-eslint/scope-manager, and @typescript-eslint/typescript-estree are also present in both versions, although crucially @typescript-eslint/types, @typescript-eslint/scope-manager, and @typescript-eslint/typescript-estree have matching version numbers to the parser, suggesting a coordinated release. The developer tooling dependencies, including glob, typescript, and @types/glob, remain consistent. The peerDependencies entry for eslint continues to specify compatibility with ESLint versions 6, 7, and 8. From a distribution perspective, file count and unpacked size are identical, indicating no significant changes in the overall package structure.

The principal difference lies in the releaseDate. Version 5.30.5 was published on July 4, 2022, while version 5.30.4 was released on July 3, 2022. While seemingly minor, this one-day gap suggests that 5.30.5 likely contains bug fixes or minor improvements discovered shortly after the release of 5.30.4. Developers should consider upgrading to version 5.30.5 to benefit from these potential enhancements and ensure they are using the most up-to-date and stable parser version. Given the tight release window, it's reasonable to expect the changes to be relatively small, but important for overall stability. The project continues to be licensed under BSD-2-Clause and actively funded via Open Collective, signalling a healthy and supported ecosystem.

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.