Finalize the App Router dev indicator on output completion (#99384)
## Summary Continue removing request-event dependencies from App Router rendering. The request body's `end` event is not a render-completion signal and may already have fired before a custom server invokes Next. Keep the dev indicator Pending until HTML or Flight output completes, then classify from render-phase dynamic API usage and route configuration, including usage discovered during Client Component SSR. Completion handling stays local and dev-only, without shared lifecycle callbacks or stream helper APIs. Actions and prefetches do not reclassify the page. HEAD requests preserve the last completed classification because their output is not consumed. Pages Router and Cache Components behavior is unchanged. ## Verification - Gated browser regressions fail before the change and pass afterward, including a Client Component that calls `unstable_noStore()` after suspending during SSR. - All 21 dev-indicator tests pass in each combination of Turbopack/Webpack and Cache Components on/off. - Isolated `pnpm test-start-webpack test/e2e/app-dir/app/standalone.test.ts` passes (2/2). <!-- NEXT_JS_LLM -->
Showing
Please
register
or
sign in
to comment