fix(deps): update dependency next to ^14.1.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
next (source)	^14.1.0 -> ^14.1.1

---

Release Notes

vercel/next.js (next)

v14.1.1

Compare Source

Core Changes

• Should not warn metadataBase missing if only absolute urls are present: https://github.com/vercel/next.js/pull/61898
• Fix trailing slash for canonical url: https://github.com/vercel/next.js/pull/62109
• Fix metadata json manifest convention: https://github.com/vercel/next.js/pull/62615
• Improve the Server Actions SWC transform: https://github.com/vercel/next.js/pull/61001
• Fix Server Reference being double registered: https://github.com/vercel/next.js/pull/61244
• Improve the Server Actions SWC transform (part 2): https://github.com/vercel/next.js/pull/62052
• Fix module-level Server Action creation with closure-closed values: https://github.com/vercel/next.js/pull/62437
• Fix draft mode invariant: https://github.com/vercel/next.js/pull/62121
• fix: babel usage with next/image: https://github.com/vercel/next.js/pull/61835
• Fix next/server api alias for ESM pkg: https://github.com/vercel/next.js/pull/61721
• Replace image optimizer IPC call with request handler: https://github.com/vercel/next.js/pull/61471
• chore: refactor image optimization to separate external/internal urls: https://github.com/vercel/next.js/pull/61172
• fix(image): warn when animated image is missing unoptimized prop: https://github.com/vercel/next.js/pull/61045
• fix(build-output): show stack during CSR bailout warning: https://github.com/vercel/next.js/pull/62594
• Fix extra swc optimizer applied to node_modules in browser layer: https://github.com/vercel/next.js/pull/62051
• fix(next-swc): Detect exports.foo from cjs_finder: https://github.com/vercel/next.js/pull/61795
• Fix attempted import error for react: https://github.com/vercel/next.js/pull/61791
• Add stack trace to client rendering bailout error: https://github.com/vercel/next.js/pull/61200
• fix router crash on revalidate + popstate: https://github.com/vercel/next.js/pull/62383
• fix loading issue when navigating to page with async metadata: https://github.com/vercel/next.js/pull/61687
• revert changes to process default routes at build: https://github.com/vercel/next.js/pull/61241
• fix parallel route top-level catch-all normalization logic to support nested explicit (non-catchall) slot routes: https://github.com/vercel/next.js/pull/60776
• Improve redirection handling: https://github.com/vercel/next.js/pull/62561
• Simplify node/edge server chunking some: https://github.com/vercel/next.js/pull/62424

Credits

Huge thanks to @​huozhi, @​shuding, @​Ethan-Arrowood, @​styfle, @​ijjk, @​ztanner, @​balazsorban44, @​kdy1, and @​williamli for helping!

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
blog	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 1, 2024 11:10pm

[github-actions]

Lighthouse Report

✨ https://blog-9lq1un394-sabertaz.vercel.app/

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	96
🟢 accessibility	100
🟡 best-practices	78
🟢 seo	100
🟢 pwa	100

✨ https://blog-9lq1un394-sabertaz.vercel.app/posts

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	99
🟢 accessibility	94
🟡 best-practices	78
🟢 seo	100
🟢 pwa	100

✨ https://blog-9lq1un394-sabertaz.vercel.app/tags

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	99
🟢 accessibility	94
🟡 best-practices	78
🟢 seo	100
🟢 pwa	100

✨ https://blog-9lq1un394-sabertaz.vercel.app/books

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	100
🟢 accessibility	94
🟡 best-practices	78
🟢 seo	100
🟢 pwa	100

✨ https://blog-9lq1un394-sabertaz.vercel.app/about

🚀 Vercel preview deployment
⚡ Lighthouse report

Category	Score
🟢 performance	98
🟢 accessibility	94
🟡 best-practices	78
🟢 seo	100
🟢 pwa	100

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@aashutoshrathi/[email protected]	None	0	10.9 kB	aashutoshrathi
npm/@hapi/[email protected]	None	0	51.5 kB	devinivy
npm/@tootallnate/[email protected]	None	0	16.3 kB	tootallnate
npm/@types/[email protected]	None	0	3 kB	types
npm/[email protected]	None	0	3.4 kB	kevva
npm/[email protected]	None	0	63.9 kB	mikemcl
npm/[email protected]	None	0	5.36 kB	sindresorhus
npm/[email protected]	None	0	6.33 kB	sindresorhus
npm/[email protected]	filesystem	0	5.75 kB	isaacs
npm/[email protected]	None	0	5.51 kB	sindresorhus
npm/[email protected]	None	0	611 B	sebmarkbage
npm/[email protected]	None	0	4.79 kB	substack
npm/[email protected]	None	0	4.86 kB	substack
npm/[email protected]	None	0	8.11 kB	thlorenz
npm/[email protected]	None	0	10.2 kB	sindresorhus
npm/[email protected]	None	0	12.3 kB	achingbrain
npm/[email protected]	None	0	82.8 kB	goto-bus-stop
npm/[email protected]	None	0	9.44 kB	hiddentao
npm/[email protected]	network	0	29.4 kB	rubenverborgh
npm/[email protected]	None	0	173 kB	pipobscure
npm/[email protected]	None	0	18.1 kB	nickfitzgerald
npm/[email protected]	None	0	12.8 kB	ljharb
npm/[email protected]	None	0	35.9 kB	kornel
npm/[email protected]	None	0	4.71 kB	rexxars
npm/[email protected]	None	0	4.4 kB	sindresorhus
npm/[email protected]	None	0	13.6 kB	indutny
npm/[email protected]	None	0	4.05 kB	qix
npm/[email protected]	None	0	2.94 kB	watson
npm/[email protected]	None	0	9.62 kB	jonschlinkert
npm/[email protected]	None	0	10.1 kB	ljharb
npm/[email protected]	environment, filesystem	0	11 kB	isaacs
npm/[email protected]	None	0	5.4 kB	dominictarr
npm/[email protected]	None	0	10.4 kB	isaacs
npm/[email protected]	None	0	1.53 MB	mcg
npm/[email protected]	None	0	5.39 kB	eventualbuddha
npm/[email protected]	None	0	75.8 kB	jdalton
npm/[email protected]	None	0	19.8 kB	jdalton
npm/[email protected]	environment	+1	20.9 kB	zertosh
npm/[email protected]	environment, filesystem	0	19.1 kB	isaacs
npm/[email protected]	None	0	24.4 kB	ai
npm/[email protected]	None	0	27.4 kB	dougwilson
npm/[email protected]	None	0	9.22 kB	jonschlinkert
npm/[email protected]	None	0	5.49 kB	sindresorhus
npm/[email protected]	None	0	4.37 kB	sindresorhus
npm/[email protected]	environment	0	5.66 kB	alexeyraspopov
npm/[email protected]	None	0	90 kB	mrmlnc
npm/[email protected]	None	0	36.7 kB	gkz
npm/[email protected]	None	0	33.5 kB	google-wombot
npm/[email protected]	None	0	8.37 kB	feross
npm/[email protected]	unsafe	0	3.42 kB	floatdrop
npm/[email protected]	None	0	32.2 kB	tim-kos
npm/[email protected]	None	0	42.3 kB	chalker
npm/[email protected]	None	0	2.83 kB	sindresorhus
npm/[email protected]	None	0	138 kB	joshglazebrook
npm/[email protected]	None	0	148 kB	7rulnik
npm/[email protected]	None	0	16.6 kB	mscdex

🚮 Removed packages: npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@babel/[email protected], npm/@jest/[email protected], npm/@jest/[email protected], npm/@jest/[email protected], npm/@jest/[email protected], npm/@sinonjs/[email protected], npm/@sinonjs/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected]

View full report↗︎