fix: use EntryKeySide in EntryKey side field (#100053)
## Summary
The serialized `side` field in `EntryKey`
(`packages/next/src/shared/lib/turbopack/entry-key.ts`) was declared
with `${EntryKeyType}` instead of `${EntryKeySide}`, so the type claimed
`side` could be `"app" | "pages" | "root" | "assets"` while
`getEntryKey` actually produces `"client" | "server"`. The `as EntryKey`
assertion on `JSON.stringify` masked the mismatch. Type-only fix;
runtime serialization is unchanged and no tests were added per the
agreed scope.
## Verification
- `pnpm --filter=next types` (after workspace bootstrap via `pnpm
build`)
- `pnpm prettier --check
packages/next/src/shared/lib/turbopack/entry-key.ts`
- Scratch tsc check (not committed): original type accepts `side:app`
literals; corrected type rejects them while still accepting keys from
`getEntryKey`
<!-- NEXT_JS_LLM -->
<!-- fleet 18629715-7a2d-41b0-8706-8b3f9db46fcc -->
Co-authored-by:
vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com>
Showing
Please
register
or
sign in
to comment