next.js
c4608008 - Add client fixes for fully static route errors (#99659)

Commit
29 days ago
Add client fixes for fully static route errors (#99659) ## Summary - add a Client fix to both runtime-data and uncached-data errors on fully static routes - document client URL hooks, browser APIs such as non-`HttpOnly` cookies, and client-side fetching as distinct patterns - keep the combined runtime-or-uncached classification in the blocking build message instead of adding a third overlay card variant - omit the Cache card when a fully static error points to `connection()`, matching the existing blocking-route behavior - align build guidance, overlay cards, error pages, and tests ## Design and capture review - [Runtime data](https://error-messages-overhaul-ibsl.labs.vercel.dev/scenario/125-ensure-static-cookies) - [Uncached data](https://error-messages-overhaul-ibsl.labs.vercel.dev/scenario/128-ensure-static-uncached) - [`connection()`](https://error-messages-overhaul-ibsl.labs.vercel.dev/scenario/129-ensure-static-connection) ## Verification - `pnpm exec jest --runInBand packages/next/src/next-devtools/dev-overlay/components/instant/instant-guidance-data.test.ts packages/next/src/next-devtools/dev-overlay/container/errors.test.ts` (139 tests passed) - Prettier and ESLint passed for the changed files - Focused e2e snapshots left to CI <!-- NEXT_JS_LLM -->
Author
Parents
Loading