Skip to content

[pull] canary from vercel:canary#804

Merged
pull[bot] merged 6 commits intoNodoY5:canaryfrom
vercel:canary
Jan 6, 2026
Merged

[pull] canary from vercel:canary#804
pull[bot] merged 6 commits intoNodoY5:canaryfrom
vercel:canary

Conversation

@pull
Copy link
Copy Markdown

@pull pull bot commented Jan 6, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

eps1lon and others added 6 commits January 6, 2026 14:44
Reverting since it produced merge conflicts with in-progress
[strict-route-types
project](https://linear.app/vercel/project/nextjs-strict-route-types-2f0a70110d5d/overview):

The lesson learned from the earlier PR was that this is a risky change.
We'll land a similar change flagged in
#87768
…d 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/

#87319 but flagged.
This auto-generated PR updates the production integration test manifest used when testing Rspack.
This auto-generated PR updates the development integration test manifest used when testing Rspack.
@pull pull bot locked and limited conversation to collaborators Jan 6, 2026
@pull pull bot added the ⤵️ pull label Jan 6, 2026
@pull pull bot merged commit 74a4af4 into NodoY5:canary Jan 6, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants