Remove dead NextNodeServer.renderHTML (#100284)
# Human Notes
This deletes some code that appears to be dead but would otherwise need
to be updated as we refactor other code nearby to pull out `request` and
`response` from inner functions.
# AI
## Summary
`NextNodeServer.renderHTML` (and its abstract declaration on
`BaseServer`) has had no callers since #81944, which removed the last
call site. Nothing else in `packages/` or `test/` references it.
This removes the method along with everything only it used:
- `lazyRenderAppPage` in `route-modules/app-page/module.render.ts`.
`lazyPrerenderAppPage` stays because export uses it.
- The `NextNodeServerSpan.renderHTML` trace span constant. It is no
longer emitted and is not in either span allowlist.
- `renderOpts.isPossibleServerAction`. `renderHTML` was its only reader.
The App Router renderer reads `isPossibleServerAction` from its render
context, not from `renderOpts`, so the Node and Edge templates no longer
need to write it. The Pages `RenderOpts` field is unchanged.
This is not public API. The `next()` custom-server wrapper (`NextServer`
in `server/next.ts`) never forwarded `renderHTML`; it only exposes the
already-deprecated `render`, `renderToHTML`, `renderError`,
`renderErrorToHTML` and `render404`. The method is `protected` on both
server classes, and the only way to reach it is by subclassing
`NextNodeServer` from `next/dist`. An override there has not run since
#81944, because nothing calls the method. The span name is not in the
span allowlists or the docs, and has not been emitted since the same PR.
There is no behavior change. This also means the App page render inputs
have one fewer producer to keep in sync when they change.
## Verification
- `tsc --noEmit` for `packages/next`: no errors
- ESLint and Prettier on the changed files
- Not run: e2e tests (the deleted code had no callers, so CI covers it)
<!-- NEXT_JS_LLM -->
---------
Co-authored-by:
Claude Opus 5.5 <noreply@anthropic.com>
Showing
Please
register
or
sign in
to comment