next.js
a3943d4e - perf(build): resolve adapter app page entries via a lookup map (#101880)

Commit
6 hours ago
perf(build): resolve adapter app page entries via a lookup map (#101880) ### What? Removes quadratic app page entry selection from the adapter's `getPrerenderFilePath` (`build-complete.ts`). ### Why? `getPrerenderFilePath` called `selectAppPageEntry` for every prerendered page. Each call re-normalized every app page key. With ~1,630 keys that came to ~2.7M `normalizeAppPath` calls. Building a lookup once cut this loop from 4.6s to 0.7s. ### How? - New `createAppPageEntryLookup` in `app-paths.ts` normalizes each app path once into a map. `selectAppPageEntry` is now a wrapper around it, so the selection rules live in one place. - The adapter builds the lookup once and reuses it for every route. ### Verification - `app-paths.test.ts` (existing tests), `pnpm --filter=next types` - `pnpm test-start-turbo test/production/adapter-config` <!-- NEXT_JS_LLM --> <!-- fleet e3595006-5386-4c4f-a82b-bf4be71c02aa --> --------- Co-authored-by: vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com>
Author
Parents
Loading