Pass App Page HMR state through a dev render context (#99487)
## Summary Continue decoupling App Router rendering from incoming request objects by capturing HMR state at the handler boundary and passing it through DevRenderContext. The context contains the HMR refresh hash and shared server-component HMR cache, and is constructed only under `next dev`. Production omits this state, and prerendering does not consume it. Rendering no longer reads the hash from request metadata. Existing upstream metadata transport and cache invalidation behavior are preserved; status and debugging callbacks are left for separate migrations. ## Verification - `pnpm test-dev-turbo test/development/app-dir/use-cache-dev/use-cache-dev.test.ts` (7 tests) - `pnpm test-dev-webpack test/development/app-dir/use-cache-dev/use-cache-dev.test.ts` (7 tests) - `pnpm test-start-webpack test/e2e/app-dir/app/standalone.test.ts` (isolated production build and Edge coverage) <!-- NEXT_JS_LLM -->
Showing
Please
register
or
sign in
to comment