Angular's TypeScript 7-Powered Compiler Enters Beta with Rust-Based

The Angular team shipped ngp, the Angular Preprocessor, a rearchitected compiler that rewrites the analysis stage of Angular's toolchain in Rust using the Oxc parsing library, clearing the way for TypeScript 7 adoption. Alex Rickabaugh and Mark Techson announced the work on the Angular team blog in late September, shortly after Microsoft shipped TypeScript 7.0, whose Go-based rewrite removed the ts.Transformer API that Angular's ahead-of-time compiler had depended on — a breaking incompatibility covered in detail by InfoQ's report.

This article covers the full technical picture: what ngp replaces, how the three-stage pipeline works, benchmark numbers from real-world codebases, how to start experimenting today, and what compatibility constraints teams must respect before switching away from ngc in production. It is aimed at Angular developers on v20 or later who want to understand what is coming in Angular 22 and how to test it now.

01Why ngc Could Not Cross the TypeScript 7 Boundary

The existing Angular compiler, ngc, wraps tsc and uses the TypeScript Transformer API to turn decorators such as @Component and @Pipe into runtime instructions at build time. TypeScript 7.0's Go-based rewrite, tsgo, removed that API entirely; the Go port offers no cross-language equivalent, and crossing the JavaScript/Go boundary at every file would be prohibitive in practice.

The Angular team's answer was to decouple Angular's compilation from TypeScript's internal APIs entirely and rebuild the analysis layer on Oxc, the VoidZero Rust toolchain that already powers Vite. The team framed this as a partial rewrite rather than a fresh start, preserving the existing TypeScript template compiler for the work TypeScript still needs to own.

02Three-Stage Pipeline Powered by Oxc and Rust

A downstream tool — tsgo, tsrs, esbuild, or Rolldown — handles type-checking and JavaScript emission independently of Angular's analysis stage. The pairing of ngp with tsrs and Rolldown delivered the fastest overall pipeline in benchmarks; tsgo with esbuild was only marginally behind. This architecture means Angular is no longer bottlenecked by any single TypeScript API's availability.

03Cold-Build and Dev-Server Speed Gains

Cédric Exbrayat of Ninja Squad benchmarked the beta across three projects and noted, "This is already very promising, and there are certainly further gains to be made when the team focuses on performance optimization." The 370,000-line commit that landed the bulk of ngp on 8 October included around 56,000 lines of Rust.

04How to Experiment with ngp Today

Teams must be on Angular v20 or later before experimenting. The standard Angular update guide brings projects up to v20; from there, Christopher Holder's vite-plugin-ngp plugin offers an on-demand compilation path for Vite-based setups.

```bash
# Upgrade to Angular v20 or later first
ng update @angular/core @angular/cli

05Install vite-plugin-ngp (prototype, pinned to 22.3.0-next.2)

Holder's plugin compiles Angular files on demand rather than upfront, which is what produced the 10.5-second first-page and 112-millisecond hot-edit results on the Super Productivity codebase (252 components). Holder cautioned that the plugin "is a prototype on a prototype" and is pinned to 22.3.0-next.2, so it is strictly experimental.

06Compatibility Limits and the Path to Angular 22

Production builds must remain on ngc until Angular 22 formally adopts ngp in a minor release. That adoption is gated on TypeScript 7.1 restoring the compiler API that Angular's downstream tooling still requires. Teams running Angular versions below v20 should complete the standard migration to v20 before testing ngp at all.

VoidZero's own experimental Oxc Angular compiler had previously reported roughly a 97-percent improvement on narrower workloads but is now described as "actively seeking maintainers." The Angular team confirmed VoidZero's work influenced ngp's architecture and that the two groups collaborated throughout, with ngp becoming the official forward path rather than a competing project.