Version Details and Security Vulnerabilities

📦

@typescript-eslint/eslint-plugin

4.27.0

Comparision Betweeen 4.27.0 and 4.26.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

422

Unpacked Size

2.14 MB

Version 4.27.0 Details

Version 4.27.0 of @typescript-eslint/eslint-plugin introduces some subtle yet important changes compared to its predecessor, version 4.26.1, making it a worthwhile upgrade for developers utilizing TypeScript and ESLint. While the core dependencies like debug, lodash, semver, regexpp, tsutils, and functional-red-black-tree remain consistent, reflecting a stable underlying infrastructure, the key difference lies in the updated internal packages: @typescript-eslint/scope-manager and @typescript-eslint/experimental-utils. These have been bumped from version 4.26.1 to 4.27.0, suggesting potential bug fixes, performance improvements, or new experimental features within the scope and utility management aspects of the plugin. The unpacked size has also slightly increased from 2246120 to 2249143, indicating the addition of new code or adjustments to existing functionalities. Developers should review the changelog for @typescript-eslint/scope-manager and @typescript-eslint/experimental-utils version 4.27.0 to understand the precise nature of these changes and how they might impact their ESLint configurations and TypeScript codebases. The release date proximity between versions (a week) and the consistent file count imply that this update is likely focused on addressing identified issues and fine-tuning existing functionalities rather than introducing radical new features. Therefore, upgrading offers a potentially smoother and more refined linting experience.

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.