TypeScript 7 launched this week with a full rewrite in Go, slashing compilation time for VS Code from 17.5 seconds to under 1.3 seconds and cutting memory use by up to 26 % in large projects. The speed boost makes everyday coding feel instant, and the savings add up to hours of developer time across the stack.

Why a Go rewrite matters

Microsoft rebuilt the compiler in Go, replacing the long-standing JavaScript/Node implementation. The original codebase hit a wall as projects grew—parsing and type-checking slowed CI runners that have limited CPU and RAM. By switching to a compiled language with built-in concurrency, the new engine runs parsing and type-checking in parallel, slashing the wait for the first error.

Real-world performance gains

Early benchmarks from a handful of major codebases illustrate the impact:

  • VS Code: 11.9 × faster compilation, 18 % lower memory footprint.
  • Sentry, Bluesky, Playwright, Tldraw: speedups from 7.7 × to 8.9 ×.
  • Bluesky also sees a 26 % drop in memory usage.

Developers who hit “run” or “watch” dozens of times a day notice smoother editing and lighter CI loads.

New flags give you control

The rewrite ships with command-line options that let teams balance speed and memory:

  • --checkers and --builders launch parsing and type-checking workers side-by-side, exploiting multicore CPUs.
  • --singleThreaded forces all work onto one thread, making debugging reproducible when a race condition appears.
  • Separate scaling of type-checking workers versus builder workers lets CI pipelines allocate just enough resources for each phase.
  • The revamped --watch mode uses a Go-based port of Parcel, dropping costly polling of massive node_modules trees and keeping file-change detection lightweight.

Who wins, and who might hesitate

Front-end frameworks that lean heavily on TypeScript—such as Next.js and Nuxt—stand to gain faster rebuilds and tighter feedback loops. IDEs like VS Code and Cursor feel more responsive, encouraging developers to stay in the editor longer instead of switching to terminal builds.

What to watch next

  • Adoption rates among large open-source projects and enterprise monorepos.
  • Community feedback on stability and any hidden performance cliffs.
  • Microsoft updates that add compiler features to further cut compile times or improve error diagnostics.