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

Key Stabilizations in Angular v22

Angular v22 introduces several API stabilizations, including Signal Forms, Angular Aria, and asynchronous reactivity APIs. Signal Forms combine the strong typing of reactive forms with the ergonomics of template-driven forms into a declarative, signal-based API. These now include full documentation and support for Angular Material and Angular Aria.

Enhanced Data Modeling and Change Detection

The release stabilizes resource, rxResource, and httpResource, providing supported methods to model asynchronous data as signals. This includes new chain() support for dependent requests and resource caching for server-side rendering. A significant change is that OnPush is now the default change detection strategy for components, replacing the previous default, which has been renamed Eager.

Improvements in Dependency Injection and Templates

Dependency injection sees enhancements with a new @Service() decorator, which replaces the common @Injectable({providedIn: 'root'}) pattern for global singletons. Additionally, injectAsync allows services to be lazily loaded and code-split, with optional prefetching during browser idle times. Template features have been expanded to include spread and rest syntax, multiple case matching, exhaustive never checks in @switch, inline arrow functions, and comments inside element tags. A developer preview of @boundary for error boundaries is planned for Q3 2026.

AI Tooling Integration

Angular v22 also ships with experimental WebMCP support, which exposes application and Signal Forms tools to in-browser AI agents. This integration includes Angular Agent Skills and stable MCP dev server tooling, aiming to support AI coding agents within the Angular ecosystem.

Community Reception

The release has generated discussion within the developer community. Some developers have expressed positive feedback regarding the usability of modern Angular and excitement for Signal Forms. However, some criticism has focused on tooling, with suggestions for Angular to reconsider its compiler due to potential integration challenges with AI code generation tools.