Why TypeScript 7.0’s Go‑rewritten Compiler Boosts Type‑Checking Speed Tenfold

Microsoft released the first release‑candidate of TypeScript 7.0, whose core change is a complete rewrite of the compiler in Go. The new implementation keeps the type‑checking logic identical to TS 6.0 but runs about ten times faster because it executes native code and uses shared‑memory parallelism.

The parallelism engine is exposed via three new command‑line flags: --checkers (sets the number of type‑checking workers, default 4), --builders (sets the number of parallel project builders), and --singleThreaded (forces single‑threaded execution). The combination of 4 checkers and 4 builders can run up to 16 type‑checking workers concurrently, so tuning is required for optimal performance. Parsing and output generation are also parallelised, yielding noticeable gains in large codebases.

File‑watch mode ( --watch) has been rewritten from Parcel’s C++ @parcel/watcher to a native Go implementation, eliminating the C++ tool‑chain dependency and reducing CPU and memory usage, especially in monorepos with tens of thousands of files.

TypeScript 7.0 introduces several breaking changes. Features deprecated in TS 6.0 such as target: es5, downlevelIteration, moduleResolution: node, and others are now hard errors. Default values for rootDir (now ./) and types have changed, requiring explicit configuration when the tsconfig.json is not in the source root. Literal type inference now follows Unicode code points instead of UTF‑16 code units, fixing long‑standing issues with emoji handling. Various JSDoc tags ( @enum, @class, @typedef) and syntax forms ( !, this aliases) have been removed or altered.

On the editor side, TypeScript 7.0 ships a new language server built on the LSP protocol that processes requests on multiple threads. Since the preview, it has added auto‑import, expanded hover, code‑lens, embedded hints, source‑definition jumps, JSX link editing, and tag completion. After the beta, semantic highlighting, import sorting, and unused‑import removal were added, and Microsoft claims language‑server command failures are more than 20× fewer than in TS 6.0.

To ease migration, Microsoft provides the @typescript/typescript6 compatibility package, allowing projects to install both TS 6.0 ( tsc6) and TS 7.0 ( tsc) side‑by‑side. The npm alias "typescript": "npm:@typescript/typescript6@^6.0.0" and the @typescript/native-preview / tsgo binaries let early adopters try the new version without custom tooling.

For CI pipelines, the parallel installation means teams can validate TS 7.0 behavior incrementally before switching. The stable release is expected about a month after the RC, with the programmatic API slated for stabilization in TS 7.1, which will allow downstream tools such as Angular, ESLint, and ts‑morph to regain native performance.