Version Details and Security Vulnerabilities

📦

@typescript-eslint/parser

8.39.0

Comparision Betweeen 8.39.0 and 8.38.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 KB

Version 8.39.0 Details

The @typescript-eslint/parser package, versions 8.39.0 and 8.38.0, serves as a crucial bridge between TypeScript code and ESLint, enabling developers to lint TypeScript projects effectively. Both versions offer an ESLint custom parser leveraging TypeScript ESTree, ensuring accurate and reliable static analysis. Core dependencies include debug, @typescript-eslint/types, @typescript-eslint/visitor-keys, @typescript-eslint/scope-manager, and @typescript-eslint/typescript-estree, reflecting the fundamental building blocks for parsing and understanding TypeScript code. Development dependencies like glob, eslint, rimraf, vitest, typescript, and @vitest/coverage-v8 support testing and development workflows.

The key difference lies primarily in the supported TypeScript version range. Version 8.39.0 expands its compatibility, declaring support for TypeScript versions ">=4.8.4 <6.0.0" in its peerDependencies. This update allows projects using TypeScript 5.9.x to seamlessly integrate with the parser, a notable improvement since version 8.38.0, which capped supported TypeScript versions at <5.9.0. Developers upgrading should note this expanded TypeScript version support for compatibility reasons. Both versions share the same license (MIT), repository details, funding information, and distribution structure (identical fileCount and unpackedSize). The releaseDate is also different showing that the version 8.39.0 has been released after 8.38.0. For developers, upgrading to 8.39.0 is recommended to keep their projects aligned with the latest TypeScript versions, gaining access to updated features and bug fixes offered by the TypeScript compiler. ```

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.