Support typescript-go for builds

[michaelhays]

Goals

When building a Next.js app, it would be great to run the typecheck with the native preview, tsgo.

This would drastically improve build times.

Proposal

I attempted to make this work locally by updating node_modules/next/, specifically by adding @typescript/native-preview as an item here, and changing the tsPath from 'typescript' to '@typescript/native-preview' here. This didn't quite work, so there is probably more effort needed here.

[CoreyCole]

the 'what works so far' section in the tsgo repo is relevant here. curious what bits next will need to wait on. huge win if local dev page compile times could be faster. this is a real log from my local dev experience in a big monorepo frontend:

✓ Compiled / in 64.6s (16717 modules)

[controversial]

I don’t think local dev builds run the typescript compiler; i think they use swc to strip types without performing type checking

[AlonMiz]

for builds the typescript is just an "additional check"
so the workaround is to disable the current check using

/** @type {import('next').NextConfig} */
const nextConfig = {
  typescript: {
    // This disables the default Next.js type check during builds
    ignoreBuildErrors: true,
  },
};

export default nextConfig;

and manually run before or after the build

tsgo --noEmit

after installing @typescript/native-preview

[evanreilly]

For running typecheck you can still do tsgo --noEmit and this will be way faster than tsc. The type checking in your live dev builds is incremental anyway so not a lot of performance to be gained after initial compilation. Will speed up next compiles once it's fully integrated but a lot of speed from incorporating tsgo into the flow as it is.

[grmkris]

any updates on this?

[MartinCura]

TS 7.0 in beta now!

Don’t let the “beta” label fool you – you can probably start using this in your day-to-day work immediately. (...) [It] is already in use in multiple multi-million line-of-code codebases both inside and outside Microsoft. It is highly stable, highly compatible, and ready to be put to the test in your daily workflows and CI pipelines today.

-- https://devblogs.microsoft.com/typescript/announcing-typescript-7-0-beta/

[smirk-dev]

This is really exciting timing because TypeScript 7.0 just hit beta on April 21, 2026 (https://devblogs.microsoft.com/typescript/announcing-typescript-7-0-beta/). The beta is available right now under the @typescript/native-preview package with the tsgo entrypoint, and Microsoft describes it as "highly stable, highly compatible, and ready to be put to the test in your daily workflows and CI pipelines today."

The performance numbers are genuinely staggering. On the Sentry codebase for example, a full build went from 133 seconds with tsc 6.0 down to 16 seconds with tsgo, roughly an 8x speedup. The gains come from two sources working together: native code compiled to machine code via Go (no JIT warmup or Node.js overhead), and parallel type checking with four workers running concurrently by default.

For Next.js integration specifically, I think the path forward might be cleaner than it seems. As @evanreilly noted above, local dev builds already use SWC for type stripping, so the immediate win is really about the next build typecheck phase. The workaround @AlonMiz shared works well today: disable the built-in check with typescript: { ignoreBuildErrors: true } and run tsgo --noEmit separately. But native integration would be far better for the ecosystem.

One thing worth tracking is that tools like typescript-eslint currently need TypeScript 6 because they import directly from the TypeScript package and the stable API for TS 7 is not ready yet. So a phased approach makes sense: support tsgo for the pure typecheck pass first, while keeping the existing path as fallback for tooling that depends on the TS language service API.

The microsoft/typescript-go repo (https://github.com/microsoft/typescript-go) has a "what works" tracker that is worth monitoring for when Next.js could flip the switch safely. Would love to see this become a first-class option in the next.config.ts type-checking configuration.

[MartinCura]

Couldn't build after moving to the TS 7 RC (https://devblogs.microsoft.com/typescript/announcing-typescript-7-0-rc/).

Worth flagging: the native-compiler detection in verify-typescript-setup.js only looks for @typescript/native-preview, but the RC now ships the native port under the canonical name (typescript@7.0.1-rc). So on a project that installed it that way, hasNecessaryDependencies flags typescript as missing (no lib/typescript.js, no root exports), the native-preview check is false, and next build dies on CI with the "do not have the required package(s) installed" error.

Workaround that's been holding up fine: add @typescript/native-preview purely as a marker dep so the existing graceful-skip branch fires. next build then logs "Detected @typescript/native-preview…" and skips its type check (real typechecking runs as a separate tsc step in CI anyway).

Would be great if the detector also recognized typescript@7.x directly so the extra dep isn't needed. Though the workaround is fine for a month until 7.0 stable drops. Cheers!

[Netail]

Next.js seems to verify if the file typescript/lib/typescript.js exists (

next.js/packages/next/src/lib/verify-typescript-setup.ts

Line 23 in aab6bf7

file: 'typescript/lib/typescript.js',

), which is not there anymore with TS7.

Also, they make use of the TypeScript API, which will land in 7.1