Version Details and Security Vulnerabilities

📦

husky

0.13.0

Comparision Betweeen 0.13.0 and 0.12.0

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

Version

Dependencies

Dev Dependencies

Peer Dependencies

Distributed Files

N/A

Unpacked Size

N/A

Version 0.13.0 Details

Husky is a popular npm package designed to prevent bad commits and pushes by leveraging Git hooks. Version 0.13.0, released on January 21, 2017, builds upon the functionality of the previous stable version, 0.12.0, released on December 14, 2016. The core purpose of Husky remains consistent: to simplify the process of working with Git hooks like pre-commit, pre-push, and post-merge, ensuring code quality and preventing common errors before they reach the repository.

A notable difference between the two versions lies in their dependencies. Version 0.13.0 introduces chalk as a dependency, using version "^1.1.3". Chalk is a widely-used package for adding styling to console output, suggesting an enhanced user experience through more informative or visually distinct messages during hook execution. In contrast, version 0.12.0 does not include chalk in its dependencies.

Both versions share the same core dependencies like is-ci, normalize-path, and find-parent-dir, highlighting the stable foundation of Husky's path resolution and CI environment detection. Additionally, both versions share the same devDependencies for mocha, expect, rimraf and mock-fs.

For developers considering Husky, both versions offer a straightforward way to manage Git hooks, improving workflow and code quality. The addition of chalk in version 0.13.0 might provide a slightly improved user experience with more visually appealing console outputs, while the core functionality for managing Git hooks remains robust in both releases. The MIT license ensures flexibility and ease of integration into various projects.

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.