Version Details and Security Vulnerabilities

📦

@typescript-eslint/parser

4.14.2

Comparision Betweeen 4.14.2 and 4.14.1

Identify the differences between the current version of the package and the previous one.

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

59.79 KB

59.62 KB

Version 4.14.2 Details

Version 4.14.2 of @typescript-eslint/parser, an ESLint custom parser leveraging TypeScript ESTree, introduces subtle but potentially important changes compared to its predecessor, version 4.14.1. Both versions share the same core functionality, description, license (BSD-2-Clause), and repository details. Key dependencies like debug, @typescript-eslint/types, @typescript-eslint/scope-manager, and @typescript-eslint/typescript-estree are updated to reflect their respective version numbers (4.14.2 and 4.14.1 accordingly), suggesting internal improvements or bug fixes within the core TypeScript-related parsing infrastructure.

The developer dependencies glob, typescript, @types/glob,@typescript-eslint/shared-fixtures and @typescript-eslint/experimental-utils are also updated. The most noticeable difference lies in the dist object. While both packages contain 12 files, the unpackedSize increases slightly from 61050 bytes in 4.14.1 to 61229 bytes in 4.14.2. This indicates minor code additions, refactoring, or potentially updated data structures. The releaseDate confirms 4.14.2 was published a week after 4.14.1, on February 1, 2021.

This package is essential for projects using TypeScript and ESLint, enabling static analysis and enforcing coding standards within TypeScript codebases, and the minor version bump likely contains targeted bug fixes and incremental improvements enhancing parsing accuracy and reliability for developers working with the latest TypeScript features. Developers should consider upgrading to 4.14.2 to benefit from these refinements, especially if encountering parsing issues in 4.14.1.

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.