Version Details and Security Vulnerabilities

📦

@typescript-eslint/eslint-plugin

4.26.1

Comparision Betweeen 4.26.1 and 4.26.0

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.26.1 Details

Version 4.26.1 of @typescript-eslint/eslint-plugin, a TypeScript plugin for ESLint, introduces subtle but potentially impactful changes compared to its predecessor, version 4.26.0. While both versions share the same core dependencies like debug, lodash, semver, regexpp, tsutils, and functional-red-black-tree, the key difference lies in the dependency versions of internal packages: @typescript-eslint/scope-manager and @typescript-eslint/experimental-utils. Version 4.26.1 bumps these internal dependencies to version 4.26.1, aligning them with the main package version, whereas 4.26.0 used version 4.26.0 for these.

This seemingly small adjustment hints at bug fixes, minor feature enhancements, or internal refactoring within the scope manager and experimental utilities. Developers should evaluate the updates carefully.

The file size increased slightly from 2245236 to 2246120. This increase indicates small changes to the code, assets or addition of small features.

For developers already utilizing @typescript-eslint/eslint-plugin, upgrading to 4.26.1 is generally recommended to benefit from the latest improvements and fixes. As always, carefully check that the new version doesn't introduce incompatibilities with your specific code base or ESLint configuration. Both rely on the same peer dependencies of eslint and parser, so there shouldn't be problems on this side but it's always advisable to test changes in a development environment before deploying for production.

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.