chore(deps): update dependency husky to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
husky	8.0.3 -> 9.1.7

---

Release Notes

typicode/husky (husky)

v9.1.7

Compare Source

v9.1.6

Compare Source

v9.1.5

Compare Source

v9.1.4

Compare Source

v9.1.3

Compare Source

• fix: better handle space in PATH

v9.1.2

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

Super saiyan god dog! It's over 9.0.0!

There's a bug with this release which prevents the deprecation notice to appear and requires to remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" (which are deprecated by the way). I'll publish a new version to fix that. Sorry about any inconvenience.

What's new

You can now run package commands directly, no need for npx or equivalents.
It makes writing hooks more intuitive and is also slightly faster 🐺⚡️

### .husky/pre-commit
- npx jest
+ jest # ~0.2s faster

A new recipe has been added to the docs. Lint staged files without external dependencies (inspired by Prettier docs). Feel free to modify it.

### .husky/pre-commit
prettier $(git diff --cached --name-only --diff-filter=ACMR | sed 's| |\\ |g') --write --ignore-unknown
git update-index --again

For more advanced use cases, see lint-staged.

Fixes

• bunx husky init command
• Workaround for some hooks implementation on Windows 🤷

Deprecations

• Remove #!/usr/bin/env sh and . "$(dirname -- "$0")/_/husky.sh" from your hooks
• Move your code from ~/.huskyrc to .config/husky/init.sh

Support for these will be removed in v10, notices have been added.

Friendly reminder

If Git hooks don't fit your workflow, you can disable Husky globally. Just add export HUSKY=0 to .config/husky/init.sh.

I've seen some confusion about this on X, so just a heads-up!

Sponsoring

Husky is downloaded over 45M times per month and used by ~1.5M projects. If your company wants to sponsor, you can do so here: GitHub Sponsors.

Have a nice summer ☀️ I'm open to new opportunities/consulting so feel free to drop me a message 😉

v9.0.11

Compare Source

• chore: update package-lock.json by @​btea in https://github.com/typicode/husky/pull/1383
• fix: husky=0 in init (fixes #​1393) by @​typicode in https://github.com/typicode/husky/pull/1395

v9.0.10

Compare Source

• fix: rename index.d.ts to index.d.mts by @​mrkjdy in https://github.com/typicode/husky/pull/1379

v9.0.9

Compare Source

• refactor: rename files by @​typicode in https://github.com/typicode/husky/pull/1378

v9.0.8

Compare Source

• docs: update index.md by @​khaledYS in https://github.com/typicode/husky/pull/1369
• Fix tab detection on install command by @​glensc in https://github.com/typicode/husky/pull/1376
• refactor: reduce file size by @​typicode in https://github.com/typicode/husky/pull/1377

v9.0.7

Compare Source

• fix: typo and source ~/.huskyrc correctly (compatibility with v8)
• docs: fix example by @​typicode in https://github.com/typicode/husky/pull/1363

v9.0.6

Compare Source

• docs: add favicon by @​rakleed in https://github.com/typicode/husky/pull/1354
• chore: apply editorconfig to code only by @​typicode in https://github.com/typicode/husky/pull/1355
• docs: update install script to mjs and fix CI checks by @​starnayuta in https://github.com/typicode/husky/pull/1357
• Fix unbound variable by @​typicode in https://github.com/typicode/husky/pull/1359

v9.0.5

Compare Source

• docs: update path to startup files by @​ManuelRauber in https://github.com/typicode/husky/pull/1350
• fix: init error by @​typicode in https://github.com/typicode/husky/pull/1353

v9.0.4

Compare Source

• fix: init create dir before by @​typicode in https://github.com/typicode/husky/pull/1348
• refactor: simplify by @​typicode in https://github.com/typicode/husky/pull/1349
• fix: init not working on pnpm #​1334 by @​rozbo in https://github.com/typicode/husky/pull/1347

v9.0.3

Compare Source

• docs: fix link by @​typicode in https://github.com/typicode/husky/pull/1340
• chore: fix links in issue template by @​julien-f in https://github.com/typicode/husky/pull/1341
• fix: add scripts field if not present by @​chalkygames123 in https://github.com/typicode/husky/pull/1338
• docs: changelog link by @​typicode in https://github.com/typicode/husky/pull/1343
• fix: insert final newline by @​chalkygames123 in https://github.com/typicode/husky/pull/1339
• fix: fix git hooks path on windows by @​rozbo in https://github.com/typicode/husky/pull/1346

v9.0.2

Compare Source

What's Changed

• fix: exit code by @​gergelypap in https://github.com/typicode/husky/pull/1336
• docs: typo by @​chalkygames123 in https://github.com/typicode/husky/pull/1337

New Contributors

• @​gergelypap made their first contribution in https://github.com/typicode/husky/pull/1336

Full Changelog: typicode/husky@v9.0.1...v9.0.2

v9.0.1

Compare Source

Kicking off the year with an exciting update!

TLDR;

Improved user experience and a (even) smaller package size while packing in more features!

👋 By the Way

I'm available for remote work (Front-end/Back-end mainly JS/TS but open to other stacks Rails, Go, Elixir). You can contact me at my mail: typicode at gmail 🙂

Introducing husky init

Adding husky to a project is now easier than ever. Although the installation process was straightforward, it often required consulting the documentation.

v8

npm pkg set scripts.prepare="husky install"
npm run prepare
npx husky add .husky/pre-commit "npm test"

v9

npx husky init

Adding a New Hook

Adding a hook is now as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic echo command.

v8

npx husky add  .husky/pre-commit "npm test"
git add --chmod=+x .husky/pre-commit # On Windows

v9

echo "npm test" > .husky/pre-commit

Further Size Reduction

v8 was already the most compact Git hooks manager at approximately 6kB.

v9 takes this a step further, reducing the size to just 3kB, likely making it the smallest devDependency in your toolkit.

To give you an idea of how small it is, the biggest file in the project is the MIT license 😄

More to Come

Additional features are in the pipeline for v9. Stay tuned 🙌

Other Changes

• Enhanced security with CI and npm --provenance for safer publishing.
• Added $XDG_CONFIG_HOME support. Move ~/.huskyrc to ~/.config/husky/init.sh for centralized configuration.
• Fixed permission issue for Windows-created hooks; they no longer need to be executable.
• Removed husky install. Use husky or husky some/dir for the same functionality (deprecation notice to be added).
• Modified behavior when .git is missing; it now triggers a warning instead of failure.
• Replaced HUSKY_DEBUG=1 with HUSKY=2 for debugging.
• Updated the Husky API for module usage.
• Transitioned to ESM for module usage.
• Dropped support for Node 14 and 16.
• Revamped docs.

How to Migrate

v9 is backward compatible with v8, allowing you to freely upgrade and migrate your hooks later.

package.json

{
  "scripts": {
-   "prepare": "husky install"
+   "prepare": "husky"
  }
}

.husky/pre-commit

- #!/usr/bin/env sh
- . "$(dirname -- "$0")/_/husky.sh"
npm test

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 743e79d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
new-web-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 18, 2024 6:07pm

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

View full report↗︎

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[socket-security]

Report too large to display inline

View full report↗︎