Angular 22 Headed Toward Stable Release

Ng-News 26/14: linkedSignal Write-Back, Error Boundaries — figure 1

The Angular team is advancing toward Angular 22, with new details emerging about what the release will include and what lies beyond it. The headline announcements this week are Angular 22 stabilization (resources, Signal Forms, @angular/aria) and compiler ABI stability across patch versions for micro frontends. Also covered: linkedSignal's set option, NgRx's reverted delegatedSignal, and error boundaries from Google I/O.

Angular 22 Stabilization

Angular 22 is approaching its release date, and information about its contents—as well as what comes after—continues to surface.

It's already known that Angular 22 will mark a number of features as stable, including resources, Signal Forms, and @angular/aria. Stable in this context means no breaking changes within a major version.

Versioning and releases * Angular

Compiler ABI and Micro Frontends

A new announcement should be welcome news for those using micro frontends with Native Federation or Module Federation. Up to this point, when loading another Angular app or micro frontend at runtime, it had to be compiled with the exact same version as the host application.

The reason is that compiled Angular code was never part of the public API and did not adhere to semantic versioning—so the Angular team could introduce breaking changes even in patch releases.

That approach is now changing. Within a major, breaking changes may still occur in minor versions, but they will no longer appear in patch versions.

docs: establish compiler abi stability across patch versions by alxhub · Pull Request #68623 · angular/angular

linkedSignal Set and delegatedSignal

Earlier episodes discussed the need for a new Signal type—similar to linkedSignal—that derives its value from another Signal without being writable. At the same time, there should be an option to write back to the source Signal.

This capability already exists internally for Signal Forms under the name DeepSignal. Since there is also demand from the wider community, NgRx, the state management library, planned to introduce it as delegatedSignal in NgRx 22. That plan has been dropped, however, and the related commit has been reverted.

Instead, linkedSignal itself will gain a set option, enabling write-back to the original Signal. In effect, the functionality that delegatedSignal would have provided will now be built directly into linkedSignal.

The PR is labeled for a minor version, indicating Angular 22.1. Last summer, the gap between 20.0 and 20.1 was about six weeks. With Angular 22 slated for the week of June 3rd, a mid-July release seems likely.

Google I/O: Error Boundaries

Google I/O took place as well, and Mark Thompson, Angular DevRel, gave a talk that introduced an upcoming feature called error boundaries.

Think of it as an elegant try/catch block for the template. Much like @defer, you wrap a section of the template with @boundary; if an error occurs, the boundary catches it and shows a fallback. Thompson also noted that retry logic might be an option for the boundary.

This should also enhance the developer experience with resources, which throw an error when you access their value.

This was the first public mention of the feature. Thompson said the plan is to ship it as a developer preview in Q3 of this year, which likely means Angular 23.

Ng-News 26/14: linkedSignal Write-Back, Error Boundaries — figure 2

Ng-News 26/14: linkedSignal Write-Back, Error Boundaries was originally published in ng-news on Medium, where people are continuing the conversation by highlighting and responding to this story.