Document route handler prerender interruptions

[DavidIlie]

What?

Documents how broad error handling in Cache Components GET Route Handlers should preserve framework-controlled prerender interruptions.

Adds TypeScript and JavaScript examples that call unstable_rethrow(error) before application error handling, and distinguishes that behavior from experimental.hideLogsAfterAbort.

Why?

Request-bound and uncached reads intentionally throw while Next.js prospectively executes a GET handler during the build. An existing try/catch can intercept that signal, log a scary-looking error, and make an expected dynamic opt-out look like a failed build.

The migration guide currently mentions log suppression but does not directly connect this Route Handler behavior to unstable_rethrow. Log suppression changes visibility only; it does not preserve framework control flow in a catch block that otherwise handles every error.

How?

Shows request.nextUrl.searchParams inside a mixed application error handler and places unstable_rethrow at the top of the catch. The surrounding text explains what each mechanism does.

Stack

Stacked on #96979, which removes the redundant second prospective execution when dynamic access was already recorded.

Verification

• npx eslint --config eslint.config.mjs docs/01-app/02-guides/migrating-to-cache-components.mdx
• Changed-file Prettier check
• Verified code-block highlight line numbers for both switcher examples

[github-actions]

Stats skipped

Commit: 1a5a9e1
View workflow run

[github-actions]

Tests Passed

Commit: 1a5a9e1