Skip to content

build: Next.js 16.3 canary + TypeScript 7 - #31

Closed
tnunamak wants to merge 1 commit into
mainfrom
feat/next-16.3-canary-ts7
Closed

build: Next.js 16.3 canary + TypeScript 7#31
tnunamak wants to merge 1 commit into
mainfrom
feat/next-16.3-canary-ts7

Conversation

@tnunamak

Copy link
Copy Markdown
Contributor

Upgrades to TypeScript 7 (the Go-native compiler) by moving Next.js to 16.3 canary, which is required to build with TS 7.

Why the canary: TS 7.0 deleted the JS Compiler API (typescript/lib/typescript.js) that Next 16.2 resolves, so next build fails on TS 7. Next PR #95639 (merged 2026-07-10) adds experimental.useTypeScriptCli, which makes Next run the local tsc directly. That flag ships in next@16.3.0-canary.93, not yet in stable 16.2.x. Moving to the canary deliberately to unblock TS 7 now; revert to 16.3 stable when it GAs.

  • next16.3.0-canary.93 (console + site)
  • typescript^7.0.2 (all 5 declaring packages)
  • experimental.useTypeScriptCli: true in both next.config.mjs

Verified: console next build --webpack compiles clean on 16.3-canary with useTypeScriptCli; site build exit 0; reference-implementation + console typechecks exit 0; test suite passes.

Note: this runs a Next.js canary in the build. Deliberate tradeoff to get TS 7 now. For maintainer review.

Closes #29.

Enable Next's TypeScript CLI so webpack production builds work with TypeScript 7.

Assisted-by: AI
Signed-off-by: Tim Nunamaker <tnunamak@gmail.com>
@tnunamak

Copy link
Copy Markdown
Contributor Author

Superseded by #44, which includes the TypeScript 7 / Next 16.3-canary update and its validation.

@tnunamak tnunamak closed this Jul 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Defer TypeScript 7 upgrade until Next.js supports it

1 participant