chore(deps): update nextjs monorepo to v14.3.0-canary.31

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@next/env (source)	14.3.0-canary.30 -> 14.3.0-canary.31
next (source)	14.3.0-canary.30 -> 14.3.0-canary.31

---

Release Notes

vercel/next.js (@​next/env)

v14.3.0-canary.31

Compare Source

Core Changes

• fix unhandled runtime error when notFound() triggered in generateMetadata w/ parallel routes: #​65102
• Use vercel deployment url for metadataBase fallbacks: #​65089
• Fix next/dynamic with babel and src dir: #​65177

Misc Changes

• Bump @testing-library/react to 15.0.3 (from 13.x): #​65119
• docs: Fix typo for ReactDOM.prefetchDNS method inside Resource Hints section: #​65111
• chore(github-workflow): update popular workflows cron time, fix undef…: #​65172
• chore(github-templates): update docs_report template, update template descriptions: #​65178

Credits

Huge thanks to @​eps1lon, @​jonathan-ingram, @​ztanner, @​samcx, and @​huozhi for helping!

---

Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), 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 these updates again.

---

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

---

This PR has been generated by Mend Renovate using a curated preset maintained by . View repository job log here

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
next-sanity-static	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 30, 2024 10:21am

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/groq@3.39.1	None	0	8.84 kB	ricokahler
npm/history@5.3.0	environment	0	121 kB	mjackson
npm/postcss@8.4.31	environment, filesystem	+3	367 kB	ai
npm/prettier@3.2.5	environment, filesystem, unsafe	0	8.39 MB	prettier-bot
npm/react-dom@18.3.1	environment	+3	4.63 MB	react-bot
npm/react@18.3.1	environment	+2	339 kB	react-bot

🚮 Removed packages: npm/@sanity/assist@3.0.3, npm/@sanity/vision@3.39.1, npm/autoprefixer@10.4.19, npm/eslint-config-prettier@9.1.0, npm/eslint-gitignore@0.1.0, npm/eslint-plugin-simple-import-sort@12.1.0, npm/groqd@0.15.11, npm/server-only@0.0.1, npm/tailwindcss@3.4.3, npm/typescript@5.4.5

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/esbuild@0.20.2	Install script: postinstall Source: node install.js	orphan: npm/esbuild@0.20.2

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/esbuild@0.20.2