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.0.0

---

Release Notes

typicode/husky (husky)

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 has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"^0.2.1" from the root project
npm ERR!   reflect-metadata@"^0.2.1" from [email protected]
npm ERR!   node_modules/typeorm-extension
npm ERR!     typeorm-extension@"^3.4.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR! node_modules/@nestjs/axios
npm ERR!   @nestjs/axios@"^3.0.1" from the root project
npm ERR!   peerOptional @nestjs/axios@"^1.0.0 || ^2.0.0 || ^3.0.0" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/terminus
npm ERR!     @nestjs/terminus@"^10.2.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.12" from @nestjs/[email protected]
npm ERR!   node_modules/@nestjs/axios
npm ERR!     @nestjs/axios@"^3.0.1" from the root project
npm ERR!     peerOptional @nestjs/axios@"^1.0.0 || ^2.0.0 || ^3.0.0" from @nestjs/[email protected]
npm ERR!     node_modules/@nestjs/terminus
npm ERR!       @nestjs/terminus@"^10.2.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-01-27T10_36_10_095Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-01-27T10_36_10_095Z-debug-0.log

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud