turbopack: only add the Pages client entry when Pages routes exist (#100896)
## Summary Only add the Pages Router client entry to the whole-app module graph when Pages Router endpoints will be emitted. Reuse the existing `/_app` endpoint condition. App Router–only builds otherwise resolve, parse, and analyze the Pages client graph without emitting it. Pages and mixed-router builds keep their existing entry. ## Verification - Pages-only change compiles independently (`cargo check -p next-api`). - App-only fixture graph: 1,074 → 955 modules. Mixed fixture builds and serves its Pages route. Separate from the AST cleanup in #100871; these PRs are independent. <!-- NEXT_JS_LLM --> <!-- I AM A HUMAN AUTHOR --> <!-- fleet 20689ccb-eff4-4cad-b89e-beeccbd8caa3 --> --------- Co-authored-by:vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com> Co-authored-by:
Luke Sandberg <210140+lukesandberg@users.noreply.github.com>
Showing
Please
register
or
sign in
to comment