Version Details and Security Vulnerabilities

📦

@typescript-eslint/parser

5.26.0

Comparision Betweeen 5.26.0 and 5.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

28.9 KB

28.95 KB

Version 5.26.0 Details

@typescript-eslint/parser version 5.26.0 introduces minor updates and refinements compared to its predecessor, version 5.25.0. While the core functionality of providing an ESLint custom parser leveraging TypeScript ESTree remains consistent, developers will notice incremental improvements in the underlying dependencies. Specifically, the package updates its internal dependencies on @typescript-eslint/types, @typescript-eslint/scope-manager, and @typescript-eslint/typescript-estree from version 5.25.0 to 5.26.0. These updates likely incorporate bug fixes, performance enhancements, and potentially new features within the broader TypeScript ESLint ecosystem.

The file sizes differ slightly, with version 5.26.0 having a unpacked size of 29591, a minor decrease compared to version 5.25.0's 29648. Both versions maintain the same essential peer dependencies, requiring an ESLint version of ^6.0.0, ^7.0.0, or ^8.0.0. This ensures compatibility with a wide range of existing ESLint configurations. Furthermore, both versions are licensed under BSD-2-Clause, providing a permissive open-source license. Developers relying on @typescript-eslint/parser should consider upgrading to version 5.26.0 to benefit from the latest bug fixes and improvements within the related packages, contributing to more reliable and efficient TypeScript linting. The release dates highlight that the newer version was released approximately one week after the older version.

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.