Sebastian "Sebbie" SilbermannandGitHub 35a566b383 [strict-route-types] Ensure cache profiles and routes are type-checked even if .next is excluded (#87768) ...

Flagged behind `experimental.strictRouteTypes`

This fixes issues where cache profiles where not included or routes not validated if `.next` was excluded to squeeze out every bit of TypeScript performance.

It also fixes a redundant type-check since we have separate dev and prod dist folders.  If you run `next dev` and (`next build` or `next typegen`), you'd type-check routes and links twice. Now `next-env.d.ts` only exists once where we decide which dist folder to type-check.

Going forward, new Next.js type-checking should be added to `next-env.d.ts`. That file is fully controlled by Next.js and churning it, does not churn users since it's not in version control.

`next-env.d.ts` will be moved into `.next` in a follow-up. Ideally independent of the dist folder i.e.  independent of `next dev` vs `next build`.

Closes https://linear.app/vercel/issue/NXT-124/

https://github.com/vercel/next.js/pull/87319 but flagged.

2026-01-06 16:21:25 +01:00

..

index.test.ts

[strict-route-types] Ensure cache profiles and routes are type-checked even if .next is excluded (#87768)

2026-01-06 16:21:25 +01:00