Version Details and Security Vulnerabilities

📦

@typescript-eslint/parser

5.36.1

Comparision Betweeen 5.36.1 and 5.36.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

29.6 KB

28.55 KB

Version 5.36.1 Details

The @typescript-eslint/parser package enables ESLint to understand and lint TypeScript code. Version 5.36.1 builds upon the previous stable version, 5.36.0, introducing subtle but potentially important changes for developers committed to code quality. Both versions share the same core function: providing an ESLint custom parser that leverages TypeScript ESTree. The key dependencies debug, @typescript-eslint/types, @typescript-eslint/scope-manager, and @typescript-eslint/typescript-estree are present in both, but their versions are consistent with the parser version. This signifies internal updates and refinements within the @typescript-eslint ecosystem to enhance parsing accuracy and maintain compatibility.

Crucially, the "dist" section reveals differences. Version 5.36.1 boasts a slightly larger unpacked size (30306 bytes vs 29234 bytes) and more files (13 vs 11) within the packaged tarball. This suggests the newer version includes added features, bug fixes, or optimized code compared to its predecessor. The release dates also pinpoint when these changes became available, with version 5.36.1 released on August 30, 2022, later than version 5.36.0. Developers should upgrade to version 5.36.1 to benefit from the latest improvements and ensure they are using the most up-to-date and reliable parser for their TypeScript ESLint configurations. Always check the changelog for detailed information about the specific changes.

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.