Version Details and Security Vulnerabilities

📦

@typescript-eslint/parser

8.30.1

Comparision Betweeen 8.30.1 and 8.30.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.01 KB

Version 8.30.1 Details

The @typescript-eslint/parser package offers developers a crucial tool for integrating TypeScript codebases with ESLint, enabling robust static analysis and code quality enforcement. Comparing versions 8.30.0 and 8.30.1 reveals subtle but important changes. Both versions maintain the same core functionality, leveraging typescript-estree to parse TypeScript code into an Abstract Syntax Tree (AST) usable by ESLint. Dependency structures are largely consistent, with shared dependencies like debug, @typescript-eslint/types, @typescript-eslint/visitor-keys, @typescript-eslint/scope-manager, and @typescript-eslint/typescript-estree ensuring a cohesive parsing experience. Development dependencies for testing and formatting such as glob, rimraf, vitest, prettier, @vitest/coverage-v8 and typescript are unchanged.

Crucially, peer dependencies remain the same, indicating continued compatibility with ESLint versions 8.57.0 and 9.x, and TypeScript versions 4.8.4 up to but not including 5.9.0. This ensures existing configurations remain valid. While the file count and unpacked size of the packages are identical, suggesting no major code restructuring, the releaseDate reveals a small time gap between the versions, hinting that version 8.30.1 likely addresses bug fixes or minor improvements not warranting a major version bump. Developers migrating from 8.30.0 should review the change log for @typescript-eslint/parser on their GitHub repository to identify the specific fixes and ensure a smooth upgrade. For many developers, the upgrade to 8.30.1 will be seamless and improve the stability of their ESLint configuration while parsing TypeScript code.

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.