Microsoft Releases TypeScript 7.0 with Native Go Compiler

Originally published at https://tekmag.thsite.top/microsoft-releases-typescript-7-0-with-native-go-compiler/

Microsoft shipped TypeScript 7.0 on July 8, 2026, delivering a complete Go-native rewrite of the compiler — the project behind a year-long codenamed initiative called Project Corsa. The new compiler claims 8x to 12x faster builds across major codebases, with VS Code itself seeing a 11.9x speedup after the migration.

Key Takeaways

• TypeScript 7.0 is a complete Go-native rewrite (Project Corsa), not a feature update — the type system is identical to TS 6.0
• Benchmarks show 8x–12x build speedups: VS Code 11.9x, Sentry 8.9x, Bluesky 8.7x, Slack CI from 7.5 min to 1.25 min
• Breaking changes include dropping ES5 target, removing AMD/UMD/SystemJS modules, deprecating baseUrl, and enforcing strict mode by default
• Migration path: upgrade to TypeScript 6.0 first, then 7.0 — the @typescript/typescript6 package is available for side-by-side use
• No stable compiler API until TypeScript 7.1; tools using the old Strada API need updates before switching

The Go Rewrite That Changed Everything

TypeScript 7.0 represents the largest architectural shift in the language's history. The compiler, previously written in TypeScript and compiled to JavaScript, has been faithfully ported to Go — not rewritten from scratch, but translated line by line while preserving the original logic and structure. The result is a compiler that executes natively, taking full advantage of modern multi-core hardware through shared-memory multithreading.

According to the official Microsoft announcement, the port was done as faithfully as possible: "writing new code while maintaining the structure and logic of the original codebase to keep results consistent and compatible between the two compilers." This means your existing TypeScript code should behave identically — the change is purely under the hood.

The project traces back to late 2024, when the TypeScript team first outlined their vision for a native port. A December 2025 progress update confirmed the team had reached a test coverage level sufficient to ship, while also acknowledging that the Strada API (the compiler's internal programmatic interface) would not be stable until TypeScript 7.1 — meaning third-party tooling vendors like typescript-eslint and ts-morph needed additional time to adapt.

Benchmark Results: The Numbers Behind the Speedup

The official TypeScript 7.0 announcement published benchmark data that validates the 10x claim across multiple real-world codebases:

• VS Code: 125.7 seconds down to 10.6 seconds (11.9x speedup)
• Sentry: 139.8 seconds down to 15.7 seconds (8.9x)
• Bluesky: 24.3 seconds down to 2.8 seconds (8.7x)
• Playwright: 12.8 seconds down to 1.47 seconds (8.7x)
• tldraw: 11.2 seconds down to 1.46 seconds (7.7x)
• Language server first error: 17.5 seconds down to under 1.3 seconds (13x faster)

Slack reported the most dramatic operational impact: their CI type-check time dropped from 7.5 minutes to 1.25 minutes. Language server crashes were reduced by 60%, and failing language server commands dropped by 80%. These numbers come directly from the companies' internal testing, as reported by InfoWorld.

Memory usage also improved, with benchmarks showing approximately 8–26% lower memory consumption across the tested codebases — a significant factor for large monorepos and CI environments.

Breaking Changes You Need to Know

TypeScript 7.0 inherits the breaking changes introduced in TypeScript 6.0 (released March 2026) and adds additional hard removals. If you're upgrading from TypeScript 5.x, you must go through 6.0 first.

Hard Removals

• target: es5 is no longer supported — ES2015 is the new minimum
• moduleResolution: node, node10, and classic have been removed entirely
• AMD, UMD, SystemJS, and None module formats are gone
• The downlevelIteration flag has been removed
• baseUrl and paths without relative paths are no longer supported
• esModuleInterop: false is now disallowed
• JSDoc @enum tag has been removed
• Closure-style type syntax is no longer recognized
• Import assertions must now use with instead of assert
• Values can no longer substitute for types in JavaScript files

New Defaults (Inherited From TypeScript 6.0)

• strict: true — always enabled
• module: esnext
• target: es2025
• moduleResolution: bundler
• esModuleInterop: true
• types: [] — empty by default; you must explicitly declare which type packages to include
• rootDir defaults to the tsconfig.json location
• noUncheckedSideEffectImports: true

Migration Guide

Microsoft's official recommendation is to upgrade to TypeScript 6.0 first, resolve any deprecation warnings, and then move to 7.0. The @typescript/typescript6 package is available for side-by-side installation if you need to run both versions during transition.

Install TypeScript 7 the same way you always have:

npm install -D typescript

The VS Code extension TypeScriptTeam.native-preview is available for developers who want to try the Go compiler before the stable release. However, Microsoft warns that the compiler API will not be stable until TypeScript 7.1, which is expected in roughly 3–4 months. Tools that depend on the Strada API — including typescript-eslint and ts-morph — will need updates before they can work with TypeScript 7.

Parallelization Controls

TypeScript 7 introduces explicit flags for tuning the parallel execution model:

• --checkers=N: controls the number of type-checker worker threads (default: 4)
• --builders=N: controls project reference builder parallelism
• --singleThreaded: disables parallelism entirely, useful for debugging or low-resource environments

These flags give developers granular control over how the compiler utilizes available CPU cores, which is particularly relevant for CI/CD pipelines where resource allocation can be tuned per-run.

Who Already Uses It?

The TypeScript 7.0 announcement lists an impressive roster of companies that tested the Go compiler before the stable release: VS Code, Slack, Bloomberg, Canva, Figma, Google, Linear, Miro, Notion, Sentry, Vercel, Xbox, Microsoft Office, and PowerBI. The breadth of adoption across both consumer and enterprise products suggests the rewrite has been thoroughly stress-tested.

For related developer tooling news, see the VS Code 1.134 release, which also touches on TypeScript integration improvements from the previous cycle. Microsoft continues to invest heavily in developer productivity, as seen with PowerToys v0.101 and other recent tooling updates.

What This Means for the Ecosystem

TypeScript 7.0's performance improvements address one of the most common complaints in the JavaScript developer community: slow type-checking on large codebases. For teams working on applications with millions of lines of TypeScript, the difference between a 10-minute type-check and a 1-minute type-check isn't just convenient — it changes the practicality of frequent type-safe development workflows.

The breaking changes, while significant, remove legacy configuration options that had been deprecated for some time. Teams that have been maintaining TypeScript 6.0 in parallel should find the migration straightforward. Those still on TypeScript 5.x or earlier will need to plan a two-step upgrade path. For context on how Microsoft approaches developer tooling upgrades, see their recent Patch Tuesday coverage.

Conclusion

TypeScript 7.0 is a landmark release that delivers on a promise made over a year ago: a compiler fast enough to make TypeScript practical at any scale. The Go rewrite, while invisible to end users, represents a fundamental shift in how the language is built and maintained. With 8x to 12x speedups verified across production codebases and a clear migration path from TypeScript 6.0, this release should accelerate adoption of the language's most advanced features — since the one thing that has historically held developers back from using TypeScript fully is its compile time.

As with any major version jump, the advice is clear: upgrade to TypeScript 6.0 first, get your codebase clean, then move to 7.0. And if you're a tooling vendor, start planning your Strada API migration now — the stable compiler API in TypeScript 7.1 will be the green light for the wider ecosystem to follow.

Frequently Asked Questions

Q: Is TypeScript 7.0 backward compatible?

TypeScript 7.0 removes several deprecated features from TypeScript 6.0, including ES5 target support, AMD/UMD/SystemJS modules, and the baseUrl/paths combination without relative paths. The type-checking logic itself is unchanged. If your code uses only features supported in TypeScript 6.0, it should work without modification.

Q: Do I need to upgrade through TypeScript 6.0 first?

Yes. Microsoft's official recommendation is to upgrade to TypeScript 6.0 first, resolve any deprecation warnings, and then move to 7.0. The @typescript/typescript6 package is available for side-by-side installation during the transition.

Q: Will my existing tools work with TypeScript 7?

Most mainstream tools already support TypeScript 7, but the compiler API will not be stable until TypeScript 7.1. Tools using the internal Strada API, such as typescript-eslint and ts-morph, may need updates. Framework-specific tooling for Vue, MDX, Astro, and Svelte may also have compatibility issues until they adopt the new LSP-based API.

Q: How do I install TypeScript 7.0?

TypeScript 7 ships as the standard typescript npm package. Run npm install -D typescript to upgrade. A VS Code extension (TypeScriptTeam.native-preview) is also available for early testing.

Q: What is Project Corsa?

Project Corsa was the internal codename for the TypeScript Go rewrite. The team methodically ported the existing TypeScript compiler to Go, maintaining structural identity with the original implementation so that type-checking results remain consistent between the two compilers.

References

1. Announcing TypeScript 7.0 — Microsoft Official Blog — Primary source for GA announcement, benchmarks, breaking changes, and migration guidance.
2. Announcing TypeScript 7.0 RC — Microsoft Official Blog — Release candidate announcement confirming 10x speed claims and parallelization controls.
3. Revving up Microsoft's 10x faster TypeScript 7 — InfoWorld — Third-party coverage of VS Code migration experience and compiler performance details.
4. Progress on TypeScript 7 — December 2025 — Microsoft — Development progress update confirming test coverage milestones and Strada API limitations.
5. TypeScript 7 Is Here: The Go Compiler Rewrite — Dennis Morello — Independent technical analysis of the port methodology and migration implications.