- 10 Jun, 2026 8 commits
-
-
next-js-bot[bot] authored
-
next-js-bot[bot] authored
-
Sebastian "Sebbie" Silbermann authored
-
next-js-bot[bot] authored
-
Sebastian "Sebbie" Silbermann authored
-
next-js-bot[bot] authored
-
Sebastian "Sebbie" Silbermann authored
-
Luke Sandberg authored
This is enabled by default in canary releases if we detect certain environment variables In the future as part of stabilization this should be handled in the build-adaptors as a more generic solution
-
- 09 Jun, 2026 25 commits
-
-
next-js-bot[bot] authored
-
Jiwon Choi authored
### What? Reverts #94617, which had reverted #94610. This re-lands the stabilization of the `catchError` API and the `retry` error prop by removing their `unstable_` prefix across source, docs, and tests. ### Why? #94610 was reverted in #94617 to unblock another change. This re-applies it now that it is no longer blocked. ### How? `git revert` of the revert commit. The repo's custom errors.json merge driver handled the error registry: the original codes `1324`/`1325` had been reclaimed by `instant` errors after the revert, so the reintroduced messages were minted as new codes `1360` (`retry()` can only be used in the App Router) and `1361` (`catchError` can only be used in Client Components), keeping errors.json append-only. The docs changelog adds `v16.3.0 | catchError became stable.` while retaining the historical `v16.2.0 | unstable_catchError introduced.` row. ### Verification - `pnpm update-error-codes` (check_error_codes passes; errors.json in sync) - `pnpm build` (full JS build, exit 0) - `pnpm --filter=next types` (exit 0) - Not run: Rust/cargo build (`react_server_components.rs` change is a one-line allow-list string revert; left to CI) <!-- NEXT_JS_LLM_PR -->
-
Joseph authored
- changes getting started -> caching - new guide for instant navs - new guide for runtime-prefetching (most pending stuff is here) - x-refs between docs - App Shell mentions in other docs (ISR w/ CC) --------- Co-authored-by:
Aurora Scharff <66901228+aurorascharff@users.noreply.github.com> Co-authored-by:
Aurora Scharff <aurora.sofie@gmail.com>
-
Aurora Scharff authored
### What? Removes `unstable_disableValidation` recommendations from all 14 insight-kind error pages and the `generateViewport` API reference. The key on `unstable_instant`'s object form is not going to ship as a recommended public API. ### Why? Each error page's **"Don't want this validation?"** block previously listed three opt-out levels: 1. **One segment** — `export const unstable_instant = false` 2. ~~**Layout and its children** — `export const unstable_instant = { unstable_disableValidation: true }`~~ ← dropped 3. **Entire app** — `experimental.instantInsights.validationLevel: 'manual-warning'` Dropping the middle bullet aligns the docs with the public-API surface we intend to keep. ### How? - Removed the `Layout and its children` bullet across 14 `errors/*.mdx` pages. - Removed the now-broken `See [Don't want this validation?] for the subtree-wide opt-out` reference in the in-body **Gotchas** sections. - Updated the `generate-viewport.mdx` API reference to drop the same dangling reference. - Framework source (`unstable_disableValidation` parsing in `app-segment-config.ts` and runtime handling in `instant-config.tsx`) is unchanged — that's a separate framework concern. <!-- NEXT_JS_LLM_PR --> -
Josh Story authored
This API has experimental modes for build validation but the dev validation is going to be stable in the next release.
-
Joseph authored
Once again, reformatting broke the highlights
-
Jiwon Choi authored
Reverts vercel/next.js#94610 Unblock
-
Jiwon Choi authored
### What? Promotes two experimental error-handling APIs to stable by dropping the `unstable_` prefix: - `unstable_catchError` → `catchError` (exported from `next/error`) - `unstable_retry` → `retry` (the prop Next.js injects into `error.js` / `global-error.js` boundaries and `catchError` fallbacks) ### Why? Both were introduced as `unstable_` in `v16.2.0` and are now stable as of `v16.3.0`. The experimental prefix should be removed from the stable surface. ### How? - Renamed the `next/error` export (`error.d.ts`, `error.js`, `src/api/error.ts`, `src/api/error.react-server.ts`) and the implementation in `client/components/catch-error.tsx`. - Renamed the framework-injected `retry` prop across `error-boundary.tsx`, `builtin/global-error.tsx`, the dev-overlay error boundary, and the `ErrorInfo` type. - Updated the RSC client-only export list in the SWC transform (`react_server_components.rs`) so importing `catchError` in a Server Component still produces the "only available in Client Components" error. - Updated the thrown error messages and their `errors.json` entries (codes 1138/1139), the TypeScript-plugin serialization-exemption rule, all affected tests, the rspack test manifests, and the docs. - Docs version-history tables keep the historical `unstable_` rows and add a `v16.3.0` row noting the rename to stable. This is a clean rename with **no** backward-compatible `unstable_` alias. ### Verification - Passed: pre-commit hooks (`prettier`, `eslint --fix`, `rustfmt`) on all 35 changed files. - Passed: repo-wide grep confirms no remaining `unstable_catchError` / `unstable_retry` outside the intended historical version-history rows. - In progress locally (covered by CI): `pnpm build-all` (native SWC still compiling on a fresh worktree), then `pnpm --filter=next types` and the targeted e2e suites (`app-dir/catch-error`, `app-dir/errors`, `rsc-build-errors`, typescript-plugin `client-boundary`). <!-- NEXT_JS_LLM_PR -->
-
Luke Sandberg authored
When launching turbopack with persistence enabled but an empty disk cache, we eagerly allocate some large `quick_cache` caches to accelerate reads. Defer this to better support the empty case which is relatively common.
-
Andrew Clark authored
Turns on `experimental.appShells` by default for projects already on `cacheComponents`, unless explicitly disabled. Thanks to the preceding router-act change, most prefetch tests pass unchanged once App Shells is enabled. A few tests are genuinely coupled to the non-App-Shells behavior — they assert on per-link or runtime prefetch responses that App Shells instead defers to navigation — so the fixtures for those tests set `appShells` back to `false`. I'll address those in follow-ups. <!-- NEXT_JS_LLM_PR -->
-
Andrew Clark authored
When App Shells is enabled, prefetching is split into two phases: a prefetch for the shell, and a separate phase for the per-page content. This would cause a handful of the existing prefetch-related tests to fail once App Shells is turned on. However, the fact that the shell is prefetched separately from the page content is an incidental detail of how prefetching works. The App Shell is conceptually part of the route, not part of the "prefetch". Or in other words, App Shell prefetching has more in common with incremental module loading than it does with prefetching in the traditional sense used in the context of web apps. So, this updates router-act to ignore App Shell requests for the purposes of making assertions about prefetch responses. They're still captured, fulfilled, and awaited — they just don't participate in the matching logic. Tests that specifically assert on App Shell behavior can opt back in with `createRouterAct(page, { includeAppShellRequests: true })`. This is groundwork for the next PR, which enables App Shells by default. With these requests ignored, most prefetch tests pass unchanged regardless of whether App Shells is on. <!-- NEXT_JS_LLM_PR --> -
Sebastian "Sebbie" Silbermann authored
-
Benjamin Woodruff authored
We reverted the use of this docker image in https://github.com/vercel/next.js/pull/94366 We're going to use GitHub actions custom runner images instead (which don't use docker)
-
Luke Sandberg authored
Add `.bin` extension to trace files This will hint to tools like tailwind that scan for content not to open these.
-
Luke Sandberg authored
`next` already disallows reading out of `.next` during a build, this extends that to the new `.next-profiles` directory This is currently hardcoded (not end user configurable), so we just hardcode the path in the next entrypoints.
-
Sam Selikoff authored
## Summary - Add regression coverage for Navigation Inspector `Continue Rendering` with a route-level `loading.tsx` - Fix Instant Navigation lock timing by snapshotting the active lock when a dynamic request starts - Prevent inspector re-arm from trapping in-flight dynamic responses behind the next capture lock ## Why The Navigation Inspector recently changed `Continue Rendering` to re-arm capture after releasing the current lock. That surfaced a race in the lower-level Instant Navigation lock handling. The flow was: 1. `Continue Rendering` deletes the `next-instant-navigation-testing` cookie. 2. Deleting the cookie releases the current navigation lock and triggers a soft refresh. 3. The inspector quickly writes a new pending cookie to re-arm capture. 4. A route-level `loading.tsx` navigation may still have dynamic data applying from the unlock-triggered refresh. 5. Before this change, `fetchMissingDynamicData` waited on whichever lock was active when the response was applied. That meant the refresh response could accidentally see the newly re-armed lock and suspend forever. This surfaced with `loading.tsx` more reliably than inline Suspense because the route-level loading boundary commits the segment loading shell, then final content depends on the unlock refresh path. Inline Suspense generally keeps the deferred dynamic work associated with the original captured navigation, so it waits on the original lock and resumes when that lock is released. ## Fix Dynamic requests now capture the current navigation lock when the request starts, then wait only on that specific lock when applying the response. This preserves the intended behavior: - Requests started during a capture still wait for that capture to release. - Requests started after unlock are not blocked by a later re-arm. - The inspector can continue re-arming capture without racing in-flight refresh responses. Conceptually, a dynamic request should wait on the lock that existed when that request started, not whatever lock happens to exist later when its response is applied.
-
Aurora Scharff authored
### What? Polishes the dev-overlay UX for the client-hook prerender error after Josh's framework fix landed in [#94494](https://github.com/vercel/next.js/pull/94494). The overlay now names the hook in the headline and shows per-hook fix cards. ### Why? Different hooks need different fixes. `useSearchParams` always suspends, but `generateStaticParams` doesn't apply to it. `useParams` is the only hook GSP resolves at build time. `usePathname` and `useSelectedLayoutSegment(s)` need a Suspense boundary or the `[block]` export. ### How? - Headline now reads "Next.js encountered URL data `useX()` in a Client Component outside of `<Suspense>`", matching the body factory wording. - Per-hook card sets in `instant-guidance-data.ts`: `useSearchParams` → Stream + Block; `useParams` → Stream + GSP + Block; `usePathname` / `useSelectedLayoutSegment(s)` → Stream + Block. - Build-time message in `ClientHookDynamicError` / `ParamClientHookDynamicError` matches the overlay card set. - Companion docs page: [vercel/front#72622](https://github.com/vercel/front/pull/72622). ### Verification Demo scenarios on the [error-messages-overhaul test app](https://error-messages-overhaul-ibsl.labs.vercel.dev/): [88-client-use-pathname](https://error-messages-overhaul-ibsl.labs.vercel.dev/scenario/88-client-use-pathname), [89-client-use-search-params](https://error-messages-overhaul-ibsl.labs.vercel.dev/scenario/89-client-use-search-params), [90-client-use-params](https://error-messages-overhaul-ibsl.labs.vercel.dev/scenario/90-client-use-params), [91-client-use-selected-layout-segment](https://error-messages-overhaul-ibsl.labs.vercel.dev/scenario/91-client-use-selected-layout-segment), [92-client-use-selected-layout-segments](https://error-messages-overhaul-ibsl.labs.vercel.dev/scenario/92-client-use-selected-layout-segments). <!-- NEXT_JS_LLM_PR --> --------- Co-authored-by:
Josh Story <gnoff@storyposted.com>
-
Hendrik Liebau authored
When Cache Components is enabled, `next dev` previously simulated a production loading experience on every cold request. The render did a prospective pass to detect cache misses, and on any miss it waited for every cache to fill via `cacheSignal.cacheReady()` and then restarted the render with warm caches before streaming anything, so the browser saw nothing until the slowest cache had filled. Every cold load blocked on cache population. This change replaces the restart-on-cache-miss flow with a single non-abandoning staged render that streams immediately and fills caches as a side effect. On a cold load the Suspense fallbacks stream right away and the cached content resolves as its cache fills; on a warm reload the staged progression matches the previous no-cache-miss path. The render is split into clearly owned pieces: `setUpStagedDevRender` builds the staged controller, cache signal, and resume cache; `streamStagedRenderInDev{Node,Web}` runs the streaming render and reports a result once the stream has fully finished; and `stagedRenderWithCachesInDev{Node,Web}` returns the stream and leaves the validation follow-up detached so it never blocks the response. The render advances its stages in sequential tasks, and the stream is not handed back the instant it exists: it is held until the render has advanced through the stage whose content belongs in the shell. That is the static stage for initial loads, HMR refreshes, and plain navigations, or the runtime stage for client navigations to a route with a runtime prefetch config, whose runtime-prefetchable content the navigation's prefetch would have settled. It never waits for the dynamic stage. Buffering the shell before the first flush keeps the streaming renderer from emitting a premature Suspense fallback for content that belongs in the shell, and it mirrors production, where the static shell (plus runtime-prefetchable content where configured) is served and the remaining holes stream in as fallbacks. Two internal reads that would otherwise register as synchronous IO and wrongly force the render to the dynamic stage, the cache handler's tag-expiry clock check and the hot reloader's module-scope dev client id, are now read untracked: via `performance.timeOrigin + performance.now()` like the `'use cache'` handler, and only in the browser where the HMR connection reads it, respectively. Cache Components rules validation now runs in that background follow-up, once the streamed render has fully settled. `planDevValidation` inspects the finished render and picks one of three paths: forward an invalid dynamic usage error the streamed render already recorded and stop (for example a request API used inside `'use cache'`); validate the streamed render's own chunks when it neither missed caches nor hit sync IO; or, when it did either, validate a dedicated warm-cache render instead. Because that warm render reads the filled caches back rather than filling them, it can surface an invalid dynamic usage error the cold streamed render cannot, such as a nested dynamic `use cache` cache life that propagated to a parent with no explicit `cacheLife`; that error is forwarded and validation is skipped, just as one recorded by the streamed render is. Since cold loads no longer block on cache fills, the transient cache-status indicator that reflected that wait is no longer emitted; a follow-up will instead add an indicator that tells the user whether a render streamed with cache misses, and so wasn't representative of production. -
Mikhail Stankevich authored
Added missing pnpm command for installing dependencies to ensure consistency with other documentation pages. <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Signed commits - This repository requires verified commit signatures on protected branches. - If this pull request is blocked for unsigned commits, re-sign the commits and force-push the branch. - A `Signed-off-by` line in the commit message is not enough. ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? Added the missing `pnpm` installation command to the `module-not-found` error documentation page. ### Why? To ensure consistency across the documentation, as other error pages and guides in Next.js typically include examples for npm, yarn, and pnpm. ### How? Added `- When using pnpm: pnpm add swr` to the "Possible Ways to Fix It" section in `errors/module-not-found.mdx`. Closes NEXT- Fixes # -->
-
Karl Horky authored
<!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Signed commits - This repository requires verified commit signatures on protected branches. - If this pull request is blocked for unsigned commits, re-sign the commits and force-push the branch. - A `Signed-off-by` line in the commit message is not enough. ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> Followup to https://github.com/vercel/next.js/pull/92786 by @icyJoseph and @feedthejim, reviewed by @aurorascharff ### What? Switch "timezone" to "time zone" ### Why? "time zone" (with a space) is the more common spelling of the term: - https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Temporal/ZonedDateTime#time_zones_and_offsets - https://date-fns.org/v4.1.0/docs/Time-Zones - https://datatracker.ietf.org/doc/rfc9557/ - https://www.iana.org/time-zones - https://www.postgresql.org/docs/current/datatype-datetime.html - https://unicode-org.github.io/icu/userguide/datetime/ - https://www.merriam-webster.com/dictionary/time%20zone ### How? Manual replacement Co-authored-by:
Joseph <joseph.chamochumbi@vercel.com>
-
Josh Story authored
-
Josh Story authored
This API is going to ship stable but some options may individually be marked unstable
-
Sam Poder authored
This PR takes the arena introduced in https://github.com/vercel/next.js/pull/94296 and uses it! It's large but shouldn't change functionality beyond the use of the arena. Some syntax related to pattern-matching had to change because `bumpalo`'s `Box` doesn't support the same pattern matching that the standard library's `Box` does but the code should be equivalent. `bumpalo`'s `Bump` type implements `Send` but not `Sync`, to allow us to pass a `Bump` into async-methods we wrap it in `ThreadLocal` (see https://docs.rs/thread_local/latest/thread_local/). `ThreadLocal` implements `Sync` by creating a new bumpalo allocator for each thread. We've tried to minimise the usage of `ThreadLocal` to just where it was needed. The downside of `ThreadLocal` is that we may find ourselves allocating memory for multiple arenas instead of just one. This is more time allocating if there are multiple threads compared to one shared allocation, however, it still appears to be a performance improvement over individually allocating memory for each `JSValue` --------- Co-authored-by:
Benjamin Woodruff <benjamin.woodruff@vercel.com>
-
Jude Gao authored
-
Josh Story authored
While force-runtime does opt you into runtime prefetching today (i.e. it does force) the intended semantic is shifting to convey that the Segment itself is designed for and makes sense (i.e. cost / performance tradeoff) to runtime prefetch. In the future segments that may be runtime prefetched might not be for various optimization reasons. We therefore are renaming the option from force-runtime to allow-runtime. In the future if we change allow-runtime to sometimes not runtime prefetch we can always ship a new force-runtime as a codemod option that recovers the current behavior. This wording also better demonstrates why this is a feature of the Segment and not say an option on the link like `<Link prefetch="force-runtime" />`.
-
- 08 Jun, 2026 7 commits
-
-
next-js-bot[bot] authored
-
Aurora Scharff authored
### What? Moves 14 insight-kind error pages from `vercel/front/apps/next-site/content/errors-extra/` into this repo's `errors/` directory. ### Why? `nextjs.org`'s sync pipeline already clones `errors/` from canary on every deploy. `errors-extra/` is meant for in-flight drafts. These pages have stabilized, so they belong with the framework code they describe. This unblocks Docs Link Validation in #94496: cross-links from this repo's API docs (`cookies.mdx`, `headers.mdx`, `use-params.mdx`, `use-pathname.mdx`, `generate-metadata.mdx`, `generate-viewport.mdx`, etc.) to `/docs/messages/blocking-prerender-*` now resolve. ### How? Copied each `.mdx` verbatim. No content changes. Frontmatter (`kind: insight`) routes them through the FixOption renderer. Follow-up PR in `vercel/front` will remove the `errors-extra/` copies; until then the override wins on slug collision but the content is byte-identical. <!-- NEXT_JS_LLM_PR -->
-
Danyal Ahmed authored
### Fixes #94499 ### Summary The `Instrumentation.onRequestError` type currently exposes the error parameter as `unknown`, but the docs described it as `Error & { digest: string }` and the example accessed `err.message` directly. This updates the docs/example to match the current type and narrows the caught value before reading `message`. ### Tests: - `git diff --check` -
Luke Sandberg authored
Enable memory eviction by default If this causes trouble setting `experimental.turbopackMemoryEviction=false` can disable this feature.
-
Joseph authored
Clarify caching directives non-persistence across deploys. - [x] reinforce that in serverless deploys, the `use cache` directive doesn't persist between requests/different instances either
-
Sam Poder authored
This PR builds on https://github.com/vercel/next.js/pull/94372. It does a similar thing but for the WebAssembly-related helpers. Collectively, these cut the run time by about 2KB (5%). The WebAssembly-related module is inserted within `turbopack-wasm/src/loader.rs`. Similar design questions to #94372 exist. `RUNTIME_ROOT` is added to `contextPrototype` and the JS-code lives in the `turbopack-wasm` package.
-
Aurora Scharff authored
### What? Tidies up how the dev overlay surfaces Issues vs Insights: - Tab bar: when there are no insights, the Insights tab is hidden. When there are no issues but there are insights, the Issues tab stays in place but reads `No issues` (disabled, no hover). - Menu row: shows one row labeled `Issues`, `Insights`, or `Issues · Insights` with a red badge for issues and an amber badge for insights, matching the trigger pill colors. ### Verification Test-app scenarios on the [error-messages-overhaul demo](https://error-messages-overhaul-ibsl.labs.vercel.dev/): [41-subnav-cookies](https://error-messages-overhaul-ibsl.labs.vercel.dev/scenario/41-subnav-cookies), [42-subnav-fetch](https://error-messages-overhaul-ibsl.labs.vercel.dev/scenario/42-subnav-fetch). ### Why? Reported by icyJoseph in Slack. The red `Issues 1` chip on an insights-only state looked like a real error; the `0/0` placeholder was inconsistent. <!-- NEXT_JS_LLM_PR -->
-