fix: mention params and searchParams in blocking-route error messages (#92360)

### What?

Adds `params` and `searchParams` to the Dynamic variant of the
blocking-route error message.

### Why?

When `const { id } = await params` in a Page component triggers the
blocking-route error, the message says "Uncached data or `connection()`
was accessed outside of `<Suspense>`" — which doesn't mention `params`
at all. This makes it hard for developers and AI agents to connect the
error to `await params` being the cause, or to find the "Params and
SearchParams" fix section in the linked error doc.

### How?

Updated two error message strings in `dynamic-rendering.ts` (and the
corresponding `errors.json` entry) to include `params` and
`searchParams` alongside "Uncached data" and `connection()`.

## PR checklist (Fixing a bug)
- Errors have a helpful link attached:
https://nextjs.org/docs/messages/blocking-route

Made with [Cursor](https://cursor.com)

Author: aurorascharff

packages/next/errors.json

@@ -1082,7 +1082,7 @@
   "1081": "Route \"%s\": Runtime data such as \\`cookies()\\`, \\`headers()\\`, \\`params\\`, or \\`searchParams\\` was accessed inside \\`generateViewport\\`. This delays the entire page from rendering, resulting in a slow user experience. Learn more: https://nextjs.org/docs/messages/next-prerender-dynamic-viewport",
   "1082": "Route \"%s\": Could not validate \\`unstable_instant\\` because a Client Component in a parent segment prevented the page from rendering.",
   "1083": "Route \"%s\": Runtime data such as \\`cookies()\\`, \\`headers()\\`, \\`params\\`, or \\`searchParams\\` was accessed outside of \\`<Suspense>\\`. This delays the entire page from rendering, resulting in a slow user experience. Learn more: https://nextjs.org/docs/messages/blocking-route",
-  "1084": "Route \"%s\": Uncached data or \\`connection()\\` was accessed outside of \\`<Suspense>\\`. This delays the entire page from rendering, resulting in a slow user experience. Learn more: https://nextjs.org/docs/messages/blocking-route",
+  "1084": "Route \"%s\": Uncached data, \\`params\\`, \\`searchParams\\`, or \\`connection()\\` was accessed outside of \\`<Suspense>\\`. This delays the entire page from rendering, resulting in a slow user experience. Learn more: https://nextjs.org/docs/messages/blocking-route",
   "1085": "Route \"%s\": Runtime data such as \\`cookies()\\`, \\`headers()\\`, \\`params\\`, or \\`searchParams\\` was accessed inside \\`generateMetadata\\` or you have file-based metadata such as icons that depend on dynamic params segments. Except for this instance, the page would have been entirely prerenderable which may have been the intended behavior. See more info here: https://nextjs.org/docs/messages/next-prerender-dynamic-metadata",
   "1086": "Route \"%s\": %s This delays the entire page from rendering, resulting in a slow user experience. Learn more: https://nextjs.org/docs/messages/next-prerender-dynamic-viewport",
   "1087": "Failed to parse \"%s\":\\n%s%s",

packages/next/src/next-devtools/dev-overlay/container/errors.tsx

@@ -225,8 +225,8 @@ function BlockingPageLoadErrorDescription({
             Viewport metadata needs to be available on page load so accessing
             data that comes from a user Request while producing it prevents
             Next.js from prerendering an initial UI.
-            <code>cookies()</code>, <code>headers()</code>, and{' '}
-            <code>searchParams</code>, are examples of Runtime data that can
+            <code>cookies()</code>, <code>headers()</code>, <code>params</code>,
+            and <code>searchParams</code> are examples of Runtime data that can
             only come from a user request.
           </p>
           <h4>To fix this:</h4>
@@ -364,9 +364,9 @@ function BlockingPageLoadErrorDescription({
         <p>
           This delays the entire page from rendering, resulting in a slow user
           experience. Next.js uses this error to ensure your app loads instantly
-          on every navigation. <code>cookies()</code>, <code>headers()</code>,
-          and <code>searchParams</code>, are examples of Runtime data that can
-          only come from a user request.
+          on every navigation. <code>cookies()</code>, <code>headers()</code>,{' '}
+          <code>params</code>, and <code>searchParams</code> are examples of
+          Runtime data that can only come from a user request.
         </p>
         <h4>To fix this:</h4>
         <p className="nextjs__blocking_page_load_error_fix_option">

packages/next/src/server/app-render/dynamic-rendering.ts

@@ -988,7 +988,7 @@ export function trackDynamicHoleInNavigation(
   const usageDescription =
     kind === DynamicHoleKind.Runtime
       ? `Runtime data such as \`cookies()\`, \`headers()\`, \`params\`, or \`searchParams\` was accessed outside of \`<Suspense>\`.`
-      : `Uncached data or \`connection()\` was accessed outside of \`<Suspense>\`.`
+      : `Uncached data, \`params\`, \`searchParams\`, or \`connection()\` was accessed outside of \`<Suspense>\`.`
   const message = `Route "${workStore.route}": ${usageDescription} This delays the entire page from rendering, resulting in a slow user experience. Learn more: https://nextjs.org/docs/messages/blocking-route`
   const error = addErrorContext(
     new Error(message),
@@ -1097,7 +1097,7 @@ export function trackDynamicHoleInRuntimeShell(
     return
   }
 
-  const message = `Route "${workStore.route}": Uncached data or \`connection()\` was accessed outside of \`<Suspense>\`. This delays the entire page from rendering, resulting in a slow user experience. Learn more: https://nextjs.org/docs/messages/blocking-route`
+  const message = `Route "${workStore.route}": Uncached data, \`params\`, \`searchParams\`, or \`connection()\` was accessed outside of \`<Suspense>\`. This delays the entire page from rendering, resulting in a slow user experience. Learn more: https://nextjs.org/docs/messages/blocking-route`
   const error = addErrorContext(new Error(message), componentStack, null)
   dynamicValidation.dynamicErrors.push(error)
   return

test/development/app-dir/cache-components-dev-fallback-validation/cache-components-dev-fallback-validation.test.ts

@@ -55,7 +55,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -84,7 +84,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -116,7 +116,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -145,7 +145,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -177,7 +177,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -206,7 +206,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -242,7 +242,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -271,7 +271,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -303,7 +303,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -332,7 +332,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -364,7 +364,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -393,7 +393,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -425,7 +425,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -454,7 +454,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -486,7 +486,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -515,7 +515,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -547,7 +547,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this:
 
@@ -576,7 +576,7 @@ describe('Cache Components Fallback Validation', () => {
          "code": "E1083",
          "description": "Runtime data was accessed outside of <Suspense>
 
-       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), and searchParams, are examples of Runtime data that can only come from a user request.
+       This delays the entire page from rendering, resulting in a slow user experience. Next.js uses this error to ensure your app loads instantly on every navigation. cookies(), headers(), params, and searchParams are examples of Runtime data that can only come from a user request.
 
        To fix this: