Urgent.News

What's breaking now, across thousands of outlets.

Tech

TypeScript 7.0 Is Rewriting the Compiler in Go

For most of its history, TypeScript has been written in TypeScript. The compiler, the language service, the checker — all JavaScript, all running on a single thread inside Node.js. That's changed now. TypeScript 7.0, shipped by Microsoft on July 8, 2026, replaces that entire implementation with a native compiler written in Go, developed under the internal codename Corsa . There's no new operator,…

TypeScript 7.0, released by Microsoft on July 8, 2026, marks a significant shift in the language's implementation. For the first time, the compiler, language service, and checker are all written in Go, a native compiler dubbed "Corsa." This move eliminates the previous reliance on JavaScript running on Node.js and introduces native code execution and multi-threaded parallelism.

The change is aimed at improving performance, particularly for large monorepos where the existing TypeScript compiler, tsc, would often grind to a halt. Microsoft evaluated several options before settling on Go, weighing its advantages as the lowest-level language that still supports native-code execution on all required platforms, with strong built-in support for concurrency.

The team chose to port the existing compiler faithfully to minimize the risk of introducing subtle type-checking differences. Performance improvements are substantial, with full builds for large projects showing an 8x to 12x speedup. Editor startup times have dropped dramatically, from around 9.6 seconds to about 1.2 seconds, and memory usage has reduced by 6% to 26% depending on project size.

The new binary, distributed as @typescript/native-preview, can be installed alongside the existing TypeScript package, allowing teams to switch incrementally and compare output before fully migrating.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Proxmox HA-Cluster: Split-Brain vermeiden & Quorum richtig einstellen

Proxmox HA-Cluster: Split-Brain verhindern und Quorum richtig konfigurieren Wer mit Proxmox VE arbeitet, weiß: Ein HA-Cluster ist die Krönung der Virtualisierungsinfrastruktur.

  • Split-Brain occurs when nodes think they're the sole cluster, leading to data inconsistencies
  • 3-node cluster requires at least 2 votes for quorum decisions
  • Configure quorum with pvecm expected command to prevent split-brain

More from Tuesday 25 August →