Version Details and Security Vulnerabilities

📦

husky

2.2.0

Comparision Betweeen 2.2.0 and 2.1.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

38.19 KB

37.37 KB

Version 2.2.0 Details

Husky is a popular npm package that simplifies the process of using Git hooks in your projects, allowing you to automate tasks before commits, pushes, and more. Versions 2.1.0 and 2.2.0 share the core functionality of preventing bad commits and pushes through Git hooks like pre-commit and pre-push. Both versions include the same set of dependencies required for core functionalities like running commands (execa), determining CI environment (is-ci), path manipulation (slash), file system searching (find-up, pkg-dir, read-pkg), Node.js process management (run-node), handling stdin (get-stdin) and configuration management (cosmiconfig and please-upgrade-node).

The key difference between husky 2.1.0 and 2.2.0 lies in the realm of package size and potentially minor bug fixes or internal improvements. Husky 2.2.0 has an unpacked size of 39110 bytes compared to 38262 bytes of husky 2.1.0, and releaseDate of 2019-05-02T03:24:24.339Z compared to 2019-04-24T21:02:13.203Z. These changes usually are not documented on minor version updates but developers are encouraged to upgrade to the latest version to benefit from the fixes.

For developers, Husky is a valuable tool for maintaining code quality and enforcing project standards. It enables automating tasks such as running linters, formatters, or tests before a commit, ensuring that only clean code is pushed to the repository. The upgrade from 2.1.0 to 2.2.0, while seemingly minor, contributes to the overall stability and potentially enhanced performance of the package. If you're already using Husky, upgrading to 2.2.0 is recommended. If you are new to Husky, it's wise to install the latest version (2.2.0 in this case) to benefit from the most up-to-date features and improvements.

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.