Description

Angular 22.x currently declares a narrow TypeScript peer dependency (>=6.0 <6.1). TypeScript 7.0 has been released, but projects cannot upgrade to it while staying on Angular 22 because @angular/compiler-cli fails at compile time (e.g. readConfiguration / DiagnosticCategory incompatibilities).

This forces teams to stay on TypeScript 6.0.x even when they want to adopt newer TypeScript language and tooling features.

Motivation

• TypeScript releases often land before Angular officially widens its peer range.
• Narrow peer ranges block legitimate upgrades and create friction for teams that track TypeScript closely.
• Clearer / broader support windows (or earlier preview support) would reduce version lock-in and avoid broken ng serve / ng build after a TypeScript bump.

Current behavior

Expected / requested behavior

1. Widen or accelerate TypeScript peer dependency support so newer TypeScript majors/minors can be adopted sooner (ideally TypeScript 7.x on Angular 22.x or the next patch/minor).
2. Document supported TypeScript ranges clearly per Angular version, and call out when a TypeScript release is intentionally unsupported.
3. Where possible, reduce coupling so minor TypeScript upgrades do not hard-break the Angular compiler CLI.

Environment

• Angular: 22.0.6
• @angular/compiler-cli: 22.0.6
• TypeScript (desired): 7.0.x
• TypeScript (working): 6.0.3
• Node.js: 22+ / 26

Additional context

This is a feature / compatibility request, not a report that Angular 22 is broken on its supported TypeScript range. The ask is to reduce TypeScript version lock-in so applications can upgrade TypeScript without waiting for a full Angular major, and without runtime/compile failures when doing so.

Thank you for considering this.