Version Details and Security Vulnerabilities

📦

@typescript-eslint/parser

8.39.1

Comparision Betweeen 8.39.1 and 8.39.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.1 Details

The @typescript-eslint/parser package serves as a bridge between TypeScript code and ESLint, allowing developers to lint their TypeScript projects effectively. Comparing versions 8.39.1 and 8.39.0 reveals subtle yet important distinctions. Both versions share the same core functionality: leveraging TypeScript ESTree to provide a custom ESLint parser. They have identical dependencies, including debug, @typescript-eslint/types, @typescript-eslint/visitor-keys, @typescript-eslint/scope-manager, and @typescript-eslint/typescript-estree, ensuring consistent internal workings. The devDependencies, such as glob, eslint, rimraf, vitest, typescript, and @vitest/coverage-v8, also remain the same, indicating no significant changes in the development or testing environment.

The peerDependencies specify compatible versions of ESLint and TypeScript, crucial for proper integration. Both versions mandate ESLint versions "^8.57.0 || ^9.0.0" and TypeScript versions ">=4.8.4 <6.0.0", stressing the importance of using compatible major versions for these tools. The license, repository, and funding details are identical, indicating no alterations in the legal or organizational aspects. The key difference lies in the version number and the release date. Version 8.39.1 was released on "2025-08-11T17:22:20.510Z", a week later than version 8.39.0's release date "2025-08-04T17:26:29.650Z". While the file count and unpacked size remain the same, this update might incorporates bug fixes, performance improvements, or minor feature enhancements not explicitly detailed in the metadata. Developers should consult the changelog for a comprehensive list of changes to assess the impact on their projects but they can expect a better and more stable linter support for Typescript.

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.