Version Details and Security Vulnerabilities

📦

@typescript-eslint/parser

5.28.0

Comparision Betweeen 5.28.0 and 5.27.1

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.28.0 Details

Version 5.28.0 of @typescript-eslint/parser represents an incremental update over version 5.27.1, primarily focusing on internal dependency synchronization and potential bug fixes—although specific bug fixes and feature additions are not explicitly detailed in the provided metadata. Developers upgrading from 5.27.1 will notice that the core dependencies, including @typescript-eslint/types, @typescript-eslint/scope-manager, and @typescript-eslint/typescript-estree, have all been bumped to version 5.28.0. This coordinated update ensures consistent behavior and compatibility across the @typescript-eslint ecosystem.

Both versions share identical development dependencies (glob, typescript, @types/glob) and peer dependencies (eslint), suggesting a stable API and tooling setup. The license, repository, and funding metadata remain consistent, indicating no change in licensing, source code location, or project support. File count and unpacked size within the distribution packages are also identical. However, a key difference lies in the substantially later releaseDate of the newer version, exactly one week after the previous release.

For developers, upgrading to 5.28.0 is encouraged to leverage the latest improvements and ensure compatibility with other @typescript-eslint packages. While the metadata doesn't explicitly define specific improvements, the coordinated version bump suggests that this new version is intended to work in sync with the other @typescript-eslint packages. Furthermore, using the most up-to-date parser contributes to staying current with TypeScript language features and best practices enforced through ESLint. Consider reviewing the release notes accompanying 5.28.0 for more detailed information on the particular fixes or improvements included.

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.