TypeScript 7.0 Native in Go: 12x Faster with True Concurrency
Microsoft releases the first version of TypeScript rewritten in Go, achieving 8x to 12x speedups in full builds and opening the door to a new tool ecosystem.
July 16, 2026 · 3 min read
TL;DR: TypeScript 7.0 rewrites the compiler in Go, achieving 8-12x faster builds thanks to native multithreading and shared memory. Available now via npm, with compatibility with TypeScript 6.0.
What Happened?
Microsoft has released TypeScript 7.0, a version that completely rewrites the original TypeScript compiler (written in TypeScript/JavaScript) in the Go language. This native port, announced on July 8, 2025, promises speedups of 8 to 12 times in full builds, according to the company (Source: InfoWorld). The new version is available via npm (npm install -D typescript) and includes a compatibility package (@typescript/typescript6) to ease the transition from TypeScript 6.0.
Why Is It Important?
TypeScript has become the de facto standard for large-scale JavaScript development, used by millions of developers. However, the original compiler, written in TypeScript itself, suffered from performance limitations on large projects. The rewrite in Go leverages the native capabilities of this language: compilation to machine code, efficient memory management, and crucially, native support for multithreading with shared memory. This allows parallelizing compilation tasks that were previously sequential, reducing wait times from minutes to seconds.
The change not only improves speed: it also lays the groundwork for future optimizations and new features. Microsoft claims the port was done faithfully maintaining the original structure and logic, ensuring full compatibility with existing code.
Consequences and Context
This move follows the trend of rewriting critical tools in systems languages for performance gains. Previous examples include esbuild (written in Go), SWC (Rust), and Rome (Rust). TypeScript 7.0 directly competes with alternatives like ts-node or Bun, which already offered fast TypeScript execution, but now the official compiler matches or exceeds those speeds.
For development teams, this means reduced continuous integration times, faster editor feedback, and lower resource consumption. Companies maintaining large TypeScript codebases (such as those using Angular, React, or Node.js) will see an immediate productivity improvement.
What Should Readers Know?
- Installation: TypeScript 7.0 installs via npm like any package. The
tsccommand now points to the new Go compiler. - Compatibility: Microsoft has released
@typescript/typescript6for those who need to keep the previous version. It can be installed side-by-side. - Performance: Internal tests show speedups of 8x to 12x in full builds. Projects that took 2 minutes now compile in 10-15 seconds.
- Future: The TypeScript team will refocus on new features and ergonomic improvements, with releases every 3-4 months.
“TypeScript 7.0 is a major milestone. This port has been the main focus of our team for over a year,” Microsoft stated in its announcement.
Technical Analysis
The choice of Go is no coincidence. Go offers a simple concurrency model (goroutines and channels) and fast compilation, ideal for command-line tools. Additionally, integration with the JavaScript ecosystem is done via WebAssembly or native bindings, though Microsoft has not detailed that aspect. Shared memory allows multiple threads to access the same abstract syntax tree (AST) without costly copies, speeding up parsing and code generation.
A potential limitation: the Go compiler cannot run directly in the browser or in environments without native binaries, but for development and CI use this is not an issue. For restricted environments, Microsoft might maintain a legacy JavaScript version, though it has not confirmed this.
Implications for the Ecosystem
TypeScript 7.0 could accelerate TypeScript adoption in projects that previously avoided it due to compilation times. It also pressures competitors like Deno (which uses V8 and Rust) and Bun (JavaScriptCore) to improve their tools. Frameworks like Next.js or SvelteKit, which depend on TypeScript compilations, will benefit directly.
In the enterprise, reduced build times translate to cost savings in CI/CD and higher developer satisfaction. Microsoft also reinforces its commitment to Go, a language already used in projects like Docker, Kubernetes, and VS Code (partially).
Conclusion
TypeScript 7.0 is not just another update: it is a deep repositioning of the compiler. By adopting Go, Microsoft solves TypeScript's main bottleneck (performance) and prepares the ground for future innovations. Developers should upgrade as soon as possible to take advantage of the speed and true concurrency. The future of TypeScript is faster, more scalable, and paradoxically, less JavaScript.