Version Details and Security Vulnerabilities

📦

@typescript-eslint/parser

8.26.0

Comparision Betweeen 8.26.0 and 8.25.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

14.16 KB

14.2 KB

Version 8.26.0 Details

Version 8.26.0 of @typescript-eslint/parser brings key updates for developers leveraging TypeScript and ESLint, specifically those working with more recent TypeScript versions. A notable change is the updated peer dependency on typescript. The new release supports TypeScript versions up to <5.9.0, expanding compatibility compared to version 8.25.0 which capped support at <5.8.0. Existing projects need to ensure they upgrade to v8.26.0 to support TypeScript 5.8.x.

Internally, all @typescript-eslint dependencies have been bumped to version 8.26.0, synchronizing the ecosystem components like @typescript-eslint/types, @typescript-eslint/visitor-keys, @typescript-eslint/scope-manager, and @typescript-eslint/typescript-estree. This ensures consistent behavior and access to the latest features and bug fixes across the board. While the devDependencies section remains generally unchanged, including tools such as jest and prettier at similar versions, the removal of @types/glob might be an indication of underlying changes in build or test processes.

The unpackedSize has slightly decreased, suggesting minor optimizations in the bundle size. Upgrading is recommended for projects aiming to maintain compatibility with the newest TypeScript releases and benefit from potential improvements or bug fixes within the parser and related modules. Developers should review their ESLint configurations and test suites after upgrading to ensure a smooth transition and continued code quality.

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.