Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://dev.to/typicode/what-s-new-in-husky-5-32g5
This PR upgrades Husky from v1 to v9, moving from the legacy JS-based hook runner to the modern core.hooksPath + shell-based architecture.
Why this change
• Husky v9 is significantly lighter and faster.
• The old v1 flow relied on JS runners and extra scaffolding, which increased overhead and required more maintenance.
• v9 reduces dependencies to zero and improves hook startup time.
What changed
• Updated Husky to v9 and regenerated the .husky/ directory.
Benefits
• Smaller install footprint.
• Faster pre-commit / pre-push execution.
• Simpler, more intuitive hooks.
• Modern and actively maintained architecture.