Version Details and Security Vulnerabilities

📦

@typescript-eslint/parser

8.7.0

Comparision Betweeen 8.7.0 and 8.6.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

18.24 KB

Version 8.7.0 Details

The @typescript-eslint/parser package, a crucial component for integrating TypeScript into ESLint workflows, has been updated from version 8.6.0 to 8.7.0. Both versions provide an ESLint custom parser that leverages TypeScript ESTree, enabling developers to lint their TypeScript code effectively. A primary difference lies in the versioning of internal dependencies. Version 8.7.0 upgrades its core dependencies: @typescript-eslint/types, @typescript-eslint/visitor-keys, @typescript-eslint/scope-manager, and @typescript-eslint/typescript-estree, all bumped from 8.6.0 to 8.7.0. This synchronization suggests that the new release addresses bugs, incorporates enhancements, or aligns with updates in the TypeScript compiler itself.

For developers, this means opting for 8.7.0 potentially grants access to the latest TypeScript language features, bug fixes within the AST (Abstract Syntax Tree) generated by TypeScript ESTree, and improvements within the scope analysis provided by the scope manager. While the devDependencies like jest, prettier, and typescript remain consistent, suggesting no major tooling changes, the underlying parsing and analysis capabilities are likely refined. The peer dependency on eslint remains unchanged, requiring either version ^8.57.0 or ^9.0.0, ensuring compatibility with recent ESLint versions. The release date reveals version 8.7.0 was published a week after 8.6.0, suggesting a rapid iteration cycle, possibly to address an urgent issue or introduce a timely feature. Developers should consult the official changelog to get detailed information about the specific changes included in version 8.7.0.

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.