Google Releases Angular v22 with Stable Signal Forms, OnPush by Default and Experimental WebMCP

What happened

Google released Angular v22, the TypeScript-first web framework from Google, with a focus on API stabilizations, more ergonomic templates, and tooling enhancements aimed at AI integration. The headline items are stable Signal Forms, OnPush change detection as the default, and experimental WebMCP. The release also introduces a new @Service() decorator for dependency injection, adds support for TypeScript 6, and removes deprecated features that had lingered from earlier API generations.

Signal Forms moving to stable means form state can sit in the same reactive graph that already drives component signals, rather than living in a parallel forms API with its own update path. OnPush by default changes how change detection is expected to run: updates are tied more tightly to explicit input and signal changes instead of broad zone-driven sweeps. The experimental WebMCP surface points at model-context style tooling hooks so AI-assisted editors and agents can reason about Angular projects with richer structure than raw file text. The @Service() decorator tightens the dependency-injection story by making service registration more declarative at the class boundary, which lines up with the broader push toward clearer, template- and DI-level ergonomics.

The technical detail

For engineers and builders, stable Signal Forms reduce the risk of building production UIs on APIs that might still shift. Teams already using signals for component state can keep form models, validation, and submission flows in one mental model instead of mixing signal-based views with older form control trees. OnPush by default rewards architectures that already pass data through inputs and signals and punishes hidden mutable state that only worked under more aggressive global change detection. Template ergonomics and AI-oriented tooling matter most for large codebases, where codegen, refactors, and review assistants need stable, discoverable APIs rather than tribal knowledge about which APIs are still experimental.

Why it matters for builders

In market terms, Angular remains Google’s primary enterprise-facing TypeScript framework, competing with other front-end stacks that have already bet heavily on fine-grained reactivity and stricter change models. Stabilizing Signal Forms and defaulting to OnPush answers a long-running critique that Angular’s reactivity story was split between legacy change detection and newer signal APIs. Experimental WebMCP and AI tooling enhancements put Angular into the same conversation as other frameworks and editor ecosystems racing to make codebases machine-readable for agents. Supporting TypeScript 6 keeps Angular aligned with the language toolchain enterprises already standardize on, while the removal of deprecated features forces a cleaner baseline for new work.

Market and competitive context

Practical next steps for teams on older Angular versions are to inventory forms usage, change-detection strategy, and any remaining deprecated APIs before planning an upgrade path to v22. Greenfield apps can start from Signal Forms and OnPush as the default posture rather than opting into modern patterns later. Anyone evaluating AI coding assistants against Angular repos should watch how experimental WebMCP is exposed in the tooling chain, because the value shows up only when editors and agents actually consume it. Dependency-injection style should be revisited where @Service() can replace more verbose provider setup, especially in libraries that want clearer service boundaries.

What to watch next

Open questions remain around how far experimental WebMCP will go before it is considered production-ready, and how painful the deprecated-feature removals will be for apps that delayed cleanup. Signal Forms stability does not by itself answer migration cost from classic reactive or template-driven forms in large applications. OnPush as the default may surface latent bugs in components that relied on broader detection without clear data inputs. Related prior art includes the multi-year signals effort inside Angular and the industry shift toward explicit reactivity in other major frameworks; v22 reads as a consolidation release that freezes those bets into the supported surface rather than a brand-new architecture story.