Version Details and Security Vulnerabilities

📦

lint-staged

9.4.0

Comparision Betweeen 9.4.0 and 9.3.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

47.63 KB

47.07 KB

Version 9.4.0 Details

Lint-staged is a popular npm package that automates code linting for staged files in Git repositories, ensuring code quality and consistency before commits. Comparing versions 9.4.0 and 9.3.0 reveals subtle but important updates for developers. Both versions share core dependencies like del, chalk, debug, execa, listr, dedent, commander, micromatch, cosmiconfig, log-symbols, string-argv, normalize-path, and stringify-object, critical for file manipulation, CLI interface, and configuration. Crucially, the please-upgrade-node dependency remains at ^3.1.1 in both, reminding users to maintain compatible Node.js versions.

The development dependencies, crucial for testing and development workflows, are also identical. These include jest, husky, eslint, fs-extra, jsonlint, prettier, babel-related tools, and various eslint plugins for Node.js, React, and code style enforcement.

The main difference lies in the distribution metadata. Version 9.4.0 has an unpacked size of 48777 bytes and was released on September 26, 2019, while version 9.3.0 has an unpacked size of 48204 bytes and was released on September 22, 2019. While the file count remains at 15 for both, the slight increase in unpacked size for 9.4.0 suggests minor bug fixes or refinements. Upgrading to 9.4.0 appears advisable to leverage these potential improvements and maintain an up-to-date linting process. Developers benefit from lint-staged by integrating it into their Git workflow using Husky, letting them automatically format and lint code changes before committing, ensuring a clean and consistent codebase.

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.