next.js

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

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)