feat(prerender): log server startup

[NathanDrake2406]

Summary

• Add a prerender-specific production server startup log that includes the actual local URL/port.
• Keep the default production server startup log unchanged for normal vinext start.
• Thread the narrow purpose: "prerender" option through app-only, pages-only, and hybrid/shared prerender server startup paths.
• Add focused coverage for Pages Router, App Router, and default production server startup logs.

Part of #563.

Validation

• vp test run tests/prod-server-logs.test.ts
• vp test run tests/prerender.test.ts -t "runPrerender — output"
• vp check tests/prod-server-logs.test.ts packages/vinext/src/server/prod-server.ts packages/vinext/src/build/prerender.ts packages/vinext/src/build/run-prerender.ts

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/vinext@1094

commit: 29842aa

[james-elicx]

/bigbonk review

[ask-bonk]

Clean, minimal change. The purpose option threads correctly through all three startup paths (app-only, pages-only, hybrid/shared), the logProdServerStarted helper is a nice consolidation of the two duplicated console.log lines, and the test coverage is solid.

One minor observation on the tests below, but nothing blocking.

[ask-bonk]

Nit: all three tests await import(...) the same module. Since Vitest (and Node) cache dynamic imports by specifier, the second and third tests will get the same module object as the first. This works today because startProdServer is a stateless function, but if it ever acquired module-level mutable state (e.g., a cached config), the tests could leak between each other.

Consider adding vi.resetModules() in the afterEach (or a beforeEach) to make each test get a fresh module instance. Not urgent — just future-proofing.

[ask-bonk]

Nice consolidation — this eliminates the duplicated log strings that previously lived in both startAppRouterServer and startPagesRouterServer.

[ask-bonk]

Review submitted. Here's a summary:

Approved -- this is a clean, well-scoped change. The purpose: "prerender" option threads correctly through all three server startup paths (startProdServer -> startAppRouterServer / startPagesRouterServer, plus the hybrid shared server in run-prerender.ts). The logProdServerStarted helper consolidates the previously duplicated console.log calls in both router servers.

One minor observation: the test file uses await import(...) for the same module across all three test cases without vi.resetModules(), so they share the same cached module instance. This works fine today since startProdServer is stateless, but adding resetModules in afterEach would future-proof against module-level state leaks.

github run