NextJS template to scaffold new project with all the default configuration
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [next](https://nextjs.org) ([source](https://redirect.github.com/vercel/next.js)) | [`^14.2.8` -> `^14.2.16`](https://renovatebot.com/diffs/npm/next/14.2.8/14.2.16) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>vercel/next.js (next)</summary> ### [`v14.2.16`](https://redirect.github.com/vercel/next.js/compare/v14.2.15...v14.2.16) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.15...v14.2.16) ### [`v14.2.15`](https://redirect.github.com/vercel/next.js/releases/tag/v14.2.15) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.14...v14.2.15) > \[!NOTE]\ > This release is backporting bug fixes. It does **not** include all pending features/changes on canary. ##### Core Changes - support breadcrumb style catch-all parallel routes [#​65063](https://redirect.github.com/vercel/next.js/issues/65063) - Provide non-dynamic segments to catch-all parallel routes [#​65233](https://redirect.github.com/vercel/next.js/issues/65233) - Fix client reference access causing metadata missing [#​70732](https://redirect.github.com/vercel/next.js/issues/70732) - feat(next/image): add support for decoding prop [#​70298](https://redirect.github.com/vercel/next.js/issues/70298) - feat(next/image): add images.localPatterns config [#​70529](https://redirect.github.com/vercel/next.js/issues/70529) - fix(next/image): handle undefined images.localPatterns config in images-manifest.json - fix: Do not omit alt on getImgProps return type, ImgProps [#​70608](https://redirect.github.com/vercel/next.js/issues/70608) - \[i18n] Routing fix [#​70761](https://redirect.github.com/vercel/next.js/issues/70761) ##### Credits Huge thanks to [@​ztanner](https://redirect.github.com/ztanner), [@​agadzik](https://redirect.github.com/agadzik), [@​huozhi](https://redirect.github.com/huozhi), [@​styfle](https://redirect.github.com/styfle), [@​icyJoseph](https://redirect.github.com/icyJoseph) and [@​wyattjoh](https://redirect.github.com/wyattjoh) for helping! ### [`v14.2.14`](https://redirect.github.com/vercel/next.js/releases/tag/v14.2.14) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.13...v14.2.14) > \[!NOTE]\ > This release is backporting bug fixes. It does **not** include all pending features/changes on canary. ##### Core Changes - Fix: clone response in first handler to prevent race ([#​70082](https://redirect.github.com/vercel/next.js/issues/70082)) ([#​70649](https://redirect.github.com/vercel/next.js/issues/70649)) - Respect reexports from metadata API routes ([#​70508](https://redirect.github.com/vercel/next.js/issues/70508)) ([#​70647](https://redirect.github.com/vercel/next.js/issues/70647)) - Externalize node binary modules for app router ([#​70646](https://redirect.github.com/vercel/next.js/issues/70646)) - Fix revalidateTag() behaviour when invoked in server components ([#​70446](https://redirect.github.com/vercel/next.js/issues/70446)) ([#​70642](https://redirect.github.com/vercel/next.js/issues/70642)) - Fix prefetch bailout detection for nested loading segments ([#​70618](https://redirect.github.com/vercel/next.js/issues/70618)) - Add missing node modules to externals ([#​70382](https://redirect.github.com/vercel/next.js/issues/70382)) - Feature: next/image: add support for images.remotePatterns.search ([#​70302](https://redirect.github.com/vercel/next.js/issues/70302)) ##### Credits Huge thanks to [@​styfle](https://redirect.github.com/styfle), [@​ztanner](https://redirect.github.com/ztanner), [@​ijjk](https://redirect.github.com/ijjk), [@​huozhi](https://redirect.github.com/huozhi) and [@​wyattjoh](https://redirect.github.com/wyattjoh) for helping! ### [`v14.2.13`](https://redirect.github.com/vercel/next.js/compare/v14.2.12...f550237aa564bd59bfef7462350ac6c502f0206d) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.12...v14.2.13) ### [`v14.2.12`](https://redirect.github.com/vercel/next.js/compare/v14.2.11...v14.2.12) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.11...v14.2.12) ### [`v14.2.11`](https://redirect.github.com/vercel/next.js/compare/v14.2.10...bfbc92aab5c727444ed21e0b84bd55cda2e22067) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.10...v14.2.11) ### [`v14.2.10`](https://redirect.github.com/vercel/next.js/compare/v14.2.9...v14.2.10) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.9...v14.2.10) ### [`v14.2.9`](https://redirect.github.com/vercel/next.js/compare/v14.2.8...v14.2.9) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.8...v14.2.9) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "before 4am on Monday" in timezone Australia/Sydney, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/Maxwell2022/next-template). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC43NC4xIiwidXBkYXRlZEluVmVyIjoiMzguMTIwLjEiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbXX0=-->
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be resolved. The issue was opened by renovate[bot] and has received 0 comments.