Version Details and Security Vulnerabilities

📦

lint-staged

10.2.4

Comparision Betweeen 10.2.4 and 10.2.3

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

Unpacked Size

73.24 KB

Version 10.2.4 Details

Lint-staged is a popular npm package that helps developers automatically lint files staged in Git before committing them, ensuring code quality and consistency. Comparing versions 10.2.4 and 10.2.3 reveals a few key differences that might be relevant to developers. Primarily, the dependency listr2 was bumped from version 2.0.1 to version 2.0.2. While seemingly minor, this could include bug fixes or performance enhancements within the listr2 library, affecting how lint-staged presents tasks and handles asynchronous operations.

Beyond this, both versions share the same core dependencies that handle functionalities like command execution (execa), glob matching (micromatch), configuration loading (cosmiconfig), and output formatting (chalk, log-symbols). The development dependencies also remain consistent, indicating that the tooling used for testing, linting, and building the package hasn't changed. These development focused libraries include utilities for testing (jest, babel-jest, consolemock), linting (eslint, prettier and respective plugins and configurations), managing git hooks (husky) and utilities to handle filesystem operations (fs-extra).

For developers, lint-staged offers a valuable tool for maintaining a clean codebase. Version 10.2.4 brings subtle improvements through the listr2 update, while retaining the stability and feature set of the 10.2.3. Always check the changelog for listr2 to observe if the new version contains important upgrades or fixes for running this package. The package itself helps teams enforce coding standards and improve code quality by running linters automatically.

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.