Version Details and Security Vulnerabilities

📦

@typescript-eslint/eslint-plugin

5.39.0

Comparision Betweeen 5.39.0 and 5.38.1

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

452

Unpacked Size

2.1 MB

Version 5.39.0 Details

The @typescript-eslint/eslint-plugin package, a vital tool for TypeScript developers using ESLint, has seen an update from version 5.38.1 to 5.39.0. This incremental release, published on October 3rd, 2022, builds upon the foundation of providing ESLint rules specifically designed for TypeScript codebases. While the core description remains the same – "TypeScript plugin for ESLint" – a closer look reveals key differences that impact developers.

The most significant change lies in the versions of internal dependencies. Components like @typescript-eslint/utils, @typescript-eslint/type-utils, and @typescript-eslint/scope-manager have all been updated from 5.38.1 to 5.39.0. These internal packages are critical for the eslint plugin to work succesfully, and the upgrade ensures developers benefit from the latest bug fixes, performance improvements, and new features implemented within these core utilities, leading to a smoother and more reliable linting experience. The update indicates a continuous effort to improve the plugin's capabilities and compatibility with evolving TypeScript features. The unpacked size has slightly increased in the new version, suggesting potentially new rules or enhanced logic added to the newer version.

The development dependencies remain the same, including tools for developing the library like chalk, marked, prettier, and typescript, indicating that the development workflow and toolchain haven't undergone significant changes. The peer dependencies, crucial for ensuring compatibility with other packages like eslint and @typescript-eslint/parser, remain consistent. Developers should confirm that they use a compatible version of these peer dependencies to avoid issues.

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.