chore(deps): update all

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/lodash (source)	4.17.6 -> 4.17.7
@types/node (source)	20.14.10 -> 20.14.13
eslint-plugin-n	17.9.0 -> 17.10.1
eslint-plugin-prettier	5.1.3 -> 5.2.1
eslint-plugin-unused-imports	4.0.0 -> 4.0.1
husky	9.0.11 -> 9.1.3
pino-pretty	11.2.1 -> 11.2.2
prettier (source)	3.3.2 -> 3.3.3
ts-jest (source)	29.2.2 -> 29.2.3
typeorm-extension	3.5.1 -> 3.6.0
typescript (source)	5.5.3 -> 5.5.4

---

Release Notes

eslint-community/eslint-plugin-n (eslint-plugin-n)

v17.10.1

Compare Source

🩹 Fixes

• Revert ts version (5.5 -> 5.4) (#​317) (3bee0d9)

v17.10.0

Compare Source

🌟 Features

• no-unsupported: Support node 20.16.0 (73e2bed)
• no-unsupported: Support node 22.3.0 and 20.16.0 (#​315) (73e2bed)
• Update to node v22.4.0 (#​310) (f7a74eb), closes #​308
• Update to node v22.5.0 (#​312) (2539c9d)

📚 Documentation

• add clarifications to readme (dbdfa8e)
• fix spacings in the example (#​306) (c092cd8)

🧹 Chores

• upgrade compatible deps (8f6f11d)

prettier/eslint-plugin-prettier (eslint-plugin-prettier)

v5.2.1

Compare Source

Patch Changes

• #​668 ac036cc Thanks @​OrlovAlexei! - build(deps): Bump synckit from 0.8.6 to 0.9.1

sweepline/eslint-plugin-unused-imports (eslint-plugin-unused-imports)

v4.0.1

Compare Source

typicode/husky (husky)

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 😉

pinojs/pino-pretty (pino-pretty)

v11.2.2

Compare Source

What's Changed

• Type fixes by @​joshkel in https://github.com/pinojs/pino-pretty/pull/522

New Contributors

• @​joshkel made their first contribution in https://github.com/pinojs/pino-pretty/pull/522

Full Changelog: pinojs/pino-pretty@v11.2.1...v11.2.2

prettier/prettier (prettier)

v3.3.3

Compare Source

diff

Add parentheses for nullish coalescing in ternary (#​16391 by @​cdignam-segment)

This change adds clarity to operator precedence.

// Input
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.2
foo ? bar ?? foo : baz;
foo ?? bar ? a : b;
a ? b : foo ?? bar;

// Prettier 3.3.3
foo ? (bar ?? foo) : baz;
(foo ?? bar) ? a : b;
a ? b : (foo ?? bar);

Add parentheses for decorator expressions (#​16458 by @​y-schneider)

Prevent parentheses around member expressions or tagged template literals from being removed to follow the stricter parsing rules of TypeScript 5.5.

// Input
@​(foo`tagged template`)
class X {}

// Prettier 3.3.2
@​foo`tagged template`
class X {}

// Prettier 3.3.3
@​(foo`tagged template`)
class X {}

Support @let declaration syntax (#​16474 by @​sosukesuzuki)

Adds support for Angular v18 @let declaration syntax.

Please see the following code example. The @let declaration allows you to define local variables within the template:

@​let name = 'Frodo';

<h1>Dashboard for {{name}}</h1>
Hello, {{name}}

For more details, please refer to the excellent blog post by the Angular Team: Introducing @​let in Angular.

We also appreciate the Angular Team for kindly answering our questions to implement this feature.

kulshekhar/ts-jest (ts-jest)

v29.2.3

Compare Source

tada5hi/typeorm-extension (typeorm-extension)

v3.6.0

Compare Source

Features

• add experimental entity-{uniqueness,property-names,join-columns} helpers (#​1062) (9ab61cc)

3.5.1 (2024-04-09)

Bug Fixes

• deps: bump locter from 2.0.2 to 2.1.0 (#​957) (34d491f)
• deps: bump reflect-metadata from 0.2.1 to 0.2.2 (#​958) (7e8e885)
• deps: bump smob from 1.4.1 to 1.5.0 (#​961) (d14f79a)
• remove extension in typeorm-extension import in seeder template file (#​954) (4ccb4b6)

Performance Improvements

• opimized seeder-factory save-many fn (#​955) (a4dfce5)

Microsoft/TypeScript (typescript)

v5.5.4

Compare Source

---

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[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 error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   dev eslint@"8.57.0" from the root project
npm error   peer eslint@"^8.56.0" from @typescript-eslint/[email protected]
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"^7.16.0" from the root project
npm error   1 more (@typescript-eslint/parser)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^9.0.0" from [email protected]
npm error node_modules/eslint-plugin-unused-imports
npm error   dev eslint-plugin-unused-imports@"^4.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-07-28T12_06_29_913Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-28T12_06_29_913Z-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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud