Version Details and Security Vulnerabilities

📦

husky

4.0.5

Comparision Betweeen 4.0.5 and 4.0.4

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.28 KB

47.25 KB

Version 4.0.5 Details

Husky is a popular npm package that simplifies the process of using Git hooks in your projects, enabling you to automate tasks before commits, pushes, and more. Version 4.0.5, released on January 10, 2020, follows closely on the heels of version 4.0.4, released just a few hours before on January 9, 2020. Both versions share the same core functionality of preventing bad commits and pushes using Git hooks, integrating seamlessly with tools like pre-commit, pre-push, and post-merge. The dependency lists for both versions remain identical, including crucial packages such as chalk for terminal styling, slash for cross-platform path handling, and cosmiconfig for configuration file management. They also share the same developer dependencies used for testing, linting, and building such as jest, eslint, typescript and related plugins.

The primary difference between the two versions lies in the underlying build process and likely bug fixes or minor improvements implemented between releases. Notably, the unpackedSize property in the dist object differs slightly: 48410 bytes for version 4.0.5, compared to 48380 bytes for version 4.0.4; also they were released with a difference of only a few hours. The tarball URLs also differ, naturally, reflecting the version number. This suggests that version 4.0.5 incorporates under-the-hood refinements. For developers, upgrading from 4.0.4 to 4.0.5 will likely be a seamless experience and is recommended to take advantage of the latest optimizations and potential bug fixes, even if the dependency list is identical. Always test after upgrading to ensure smooth integration with your existing workflow.

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.