Version Details and Security Vulnerabilities

📦

lint-staged

13.0.0

Comparision Betweeen 13.0.0 and 12.5.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

104.03 KB

103.9 KB

Version 13.0.0 Details

Lint-staged version 13.0.0 introduces notable updates compared to version 12.5.0, impacting developers utilizing this tool for Git pre-commit hooks. A key difference lies in the dependencies. Version 13.0.0 upgrades the yaml dependency from ^1.10.2 to ^2.1.1 and execa from ^5.1.1 to ^6.1.0, potentially bringing performance improvements, new features, or bug fixes associated with these updated packages. Version 12.5.0 had supports-color dependency at 9.2.2 but version 13.0.0 does not have that dependency. No other changes are visible on the dev dependencies.

Developers should be aware of these dependency updates, as they might require adjustments in their configurations or workflows to ensure compatibility. The upgrade in yaml package could affect how the lint-staged configuration file is parsed, while the execa upgrade could change how external commands are executed. Lint-staged continues to provide a seamless way to run linters on staged files, ensuring code quality and consistency before commits. Keep in mind that the library continues to have the same MIT license, the same author and the same funding URL. Both distributions have the same amount of files and very similar unpacked size.

Before upgrading, developers should thoroughly test the new version in a development environment to identify any potential issues or incompatibilities. Reviewing the changelogs for yaml and execa is highly recommended to understand the specific changes introduced in these updated dependencies.

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.