DEV Community: Playful Programming Angular

Angular Addicts #51: spartan/ui 1.0, A2UI, Signal Debouncing & more

Gergely Szerovay — Thu, 16 Jul 2026 08:31:30 +0000

👋Hey fellow Angular Addict

This is the 51st issue of the Angular Addicts Newsletter, a monthly collection of carefully selected Angular resources that caught my attention. (Here are the 50th, 49th and 48th)

📢 Release announcements

📢 Announcing spartan/ui 1.0

By Robin Goetz

💎Angular Gems of June, 2026

📰 Agentic Engineering: How to Set Up Your Harness for Angular Development

By Alexander Thalhammer

📰 Getting to Know Angular Resource Snapshots

By Fanis Prodromou

📰 Making the Context Across 46 Repositories Semantically Searchable for AI (Part 2)

By Ryosuke Tsuji

👨‍💻About the author

My name is Gergely Szerovay, I worked as a data scientist and full-stack developer for many years, and I have been working as frontend tech lead, focusing on Angular based frontend development. As part of my role, I'm constantly following how Angular and the frontend development scene in general is evolving. To share my knowledge, I started the Angular Addicts monthly newsletter and publication in 2022, so that I can send you the best resources I come across each month. Whether you are a seasoned Angular Addict or a beginner, I got you covered. Let me know if you would like to be included as a writer. Let’s learn Angular together! Subscribe here 🔥

Follow me on Substack (Angular Addicts), Substack (AIBoosted.dev), Medium, Dev.to, Twitter or LinkedIn to learn more about Angular, and how to build AI apps with AI, Typescript, React and Angular!

🕹️Previous issues

If you missed the previous issues of the newsletter, you can read them here, these are the latest 3 issues:

📨 Submit your Angular resource

Have you found or written an interesting Angular-related article, tweet or other resource lately? Please let me know here in the comments or send me a DM on Twitter! I might feature it in the next Angular Addicts issue!

Ng-News 26/17: PrimeNG's New Licensing, and A2UI for Angular

ng-news — Mon, 13 Jul 2026 15:18:58 +0000

PrimeNG's new licensing model and A2UI for model-controlled Angular interfaces are the headline topics this week.

Also in brief: OpenNG's community fork, transactional router resource behavior, and the current Native Federation and Module Federation options for Angular.

Future of PrimeNG

PrimeNG, a very popular UI component library, has announced that future major versions won't be available as open source anymore, except through a free Community license for individuals, students, non-profits, non-commercial open source projects, and small organizations.

That doesn't just apply to the Angular version but to the React and Vue versions as well. The reason is that the library has grown over time, which means if you do this as open source you have to spend much more time on it, and at some point, the income that they got from selling things around the library itself didn't cover the costs anymore.

The new licensing brand is PrimeUI. The launch price is USD 599 per developer. That is perpetual, so for life for the covered versions, and it includes one year of updates. It also includes PrimeUI PRO, which contains components for charts, text editor, scheduler, task board, and more. The Pro components are not part of the Community license.

PrimeUI

PrimeUI is a complete UI ecosystem — premium component libraries, advanced pro components, UI kit, and design resources to build modern web applications.

primeui.dev

That being said, OpenNG, an organization which maintains unmaintained libraries, announced that PrimeNG went closed-source, the GitHub repository was archived on June 28th, 2026, and OpenNG created a copy of the project with regenerated open issues and PRs. Their goal is to release a beta version supporting Angular 22. So we are talking here about a fork. At the time of this writing, the current name is open-prime, but OpenNG says it is too close to PrimeNG because PrimeTek plans to put trademarks on it.

OpenNG Update: Funding, Versioning, PrimeNG and ngneat projects | OpenNG posted on the topic | LinkedIn

As people have questions about the future of projects such as Spectator or PrimeNG, here is the current state of our actions. OpenNG We just renamed the initiative from OpenNG Foundation to OpenNG to avoid confusion and to respect the OpenJS Foundation trademark policy. Funding We are working on a funding model to support the maintenance of the projects and give back to contributors. We submitted the initiative to Open Collective and contacted HeroDevs for partnership. Versioning Policy We'll start over with v1.0.0 for all the packages. Each project will include a matrix compatibility table with the supported major Angular versions (including the previous package). Some packages were already not following the Angular versioning policy, and this will allow us to author a major version for breaking changes anytime. PrimeNG PrimeNG went closed-source, and the GitHub repository was archived on June 28th, 2026. Discover the announcement here. We created a copy of the project and regenerated the open issues/PRs. Out of 968 open issues, 58 have already been closed, and 23 triaged as still relevant and accepting contributions to resolve them. Triaging was made possible thanks to the contribution of the community. Our goal this week is to release a beta version supporting Angular 22, as people were already delaying updating their projects. It'll include: - a set of unreleased changes from the original repository (modernize existing components, add a few new ones) - ng add support for new projects - ng update support as unreleased changes include a few breaking changes (camelcase selectors removed, deprecated APIs removed) Our current blocker for this release is to find a proper name for the project. Currently named open-prime, it's too close to PrimeNG as PrimeTek plans to put trademarks on it. We asked the community for suggestions here. We're evaluating proposals, with the main restriction being to avoid confusion with another project (many UI frameworks are matching the proposals). ngneat projects Out of the 34 original repositories, we decided to start working on the following ones: - cashew - query - elf - spectator We have a volunteer working on cashew, currently preparing the first release. Spectator is our priority within the ngneat ecosystem, planning a release this week. We also have a contribution to expose the jasmine package as a standalone (like jest/vitest ones, planned to land in 1.1.0. We still need to triage the remaining repositories to understand if we should keep them or not. 13 of them might not be maintained anymore due to low activity or having a better alternative nowadays. GitHub: https://lnkd.in/eE7QuzZR

linkedin.com

A2UI

Devin Chasanoff from the Angular team has published an article on how to use A2UI with Angular, which enables dynamic UI that is controlled by an AI model.

The user expresses an intent through the frontend. The frontend sends that intent and relevant context to a model. This communication can also include a component catalog that the frontend knows how to render. The model can then decide whether UI components are needed, which components are appropriate, and return structured UI instructions to the application.

A2UI is a protocol used for these agent-generated UI use cases. A2UI messages can be transported over HTTP, WebSocket, or Server-Sent Events, depending on the application architecture.

Demystifying A2UI: How to Make AI Agents “Speak UI” in Your App | by Devin Chasanoff | Jun, 2026 | Angular Blog

I’ve spent a fair amount of time experimenting with A2UI, a protocol for building agentic interfaces. Why? Quite simply, because I think…

blog.angular.dev

routerResource

In other news, work on integrating resource behavior with the router seems to have begun. A PR meant for internal usage popped up, which uses a snapshot-like router resource behavior to integrate navigation-specific information.

That snapshot would freeze a resource's state, for example the value, while a navigation happens. Once the navigation succeeds, the underlying value is exposed, and if the navigation is cancelled, the frozen value would still be there during rollback recovery.

Imagine the following use case. A resource has a router parameter as its own parameter. That could be a product id which loads a product by id. If the user stays on the same component but navigates to a different product id, the resource would immediately change its state and the UI would change while the navigation happens. That could cause flickering effects, especially if the navigation gets cancelled via a guard and the product id changes back to its initial value.

With the introduced router resource behavior, that is not going to happen. Again, the PR's description explicitly states that this is not currently exposed for public use, but it is very likely the start to get resources and the router together.

Angular PR #69490: Create transactional router resource

Micro-Frontends

In other news, going with Micro-Frontends is an architectural need which we find very often in enterprises. Although they are not an Angular framework feature, there are two common community solutions in the form of Native Federation and Module Federation.

The main distinction in Angular is that Native Federation works with esbuild, so the modern Angular builder, and Module Federation traditionally works with the old webpack builder or alternative builders such as Rspack.

Native Federation is maintained by Angular Architects, and Module Federation support in Nx has been common for Angular workspaces. In the release blog for Nx 23, Nx now recommends @angular-architects/native-federation for Angular and deprecates the older Nx-specific Module Federation generators and executors.

Nx 23: 4x Faster Nx Agents, Agentic Nx Migrate, improved targetDefaults, .Net GA | Nx Blog

Nx 23 brings a smarter multi-major nx migrate, performance wins across the local engine and Nx Cloud agents, native Node.js TypeScript stripping and V8 compile cache on by default, more precise target configuration, and a big cleanup of deprecated generators, executors, and APIs.

nx.dev

Ng-News 26/16: OpenNG Foundation, spartan/ui

ng-news — Thu, 02 Jul 2026 21:47:45 +0000

OpenNG Foundation and spartan/ui 1.0 are the headline topics this week: a new home for libraries like Spectator and Elf, and spartan/ui, a stable shadcn-inspired component library for Angular.

Also in brief: Storybook's Angular modernization through AnalogJS, the end of ng-conf, and AI Dev Craft in Las Vegas.

OpenNG Foundation

Maintaining open-source libraries is hard work. Developers often do it in their spare time, committing to years of maintenance, adding new features, and responding to user requests.

Last episode, we reported that the ngneat organization was taken down for unknown reasons. While we still don't know why it happened, a new home has emerged for its popular libraries like Spectator and Elf: the OpenNG Foundation.

Gerome Grignon, known for CanIUseAngular and as the organizer of Ng-Baguette, announced the foundation, which is already hosting these libraries. Alongside Gerome, the current OpenNG team also includes Dominic Bachmann, organizer of Angular Lucerne and author of the angular-typed-router library.

OpenNG Foundation · GitHub

OpenNG Foundation has 8 repositories available. Follow their code on GitHub.

github.com

spartan/ui 1.0

spartan/ui has officially released its 1.0 version. It provides an "accessible, production-ready library of more than 55 components" with fully customizable styling.

After debuting in August 2023 with 30 primitives, it now reaches stable in 2026 with a modern architecture built around signals, standalone components, zoneless change detection, and SSR. Originally initiated by Robin Götz, a full team quickly formed around the project.

spartan/ui can be seen as the Angular equivalent to shadcn/ui, famous for its customizability. While similar open-source alternatives exist, spartan/ui was the pioneer and has a proven track record of active maintenance over the years.

Robin Goetz for Playful Programming Angular

Jun 24

Announcing spartan/ui 1.0

#angular #webdev

3 min read

AnalogJS in Storybook

Storybook’s Angular integration is getting a modernization, and it is all thanks to AnalogJS.

While modern versions of the Angular CLI use Vite under the hood as a development server, it remains a "black box." The Angular CLI is still the one managing the compilation. Because the CLI itself is not a Vite plugin, it cannot be easily plugged into other modern tools.

And that's the issue for Storybook, Vitest, but also others. They are designed to support any framework that presents itself as a Vite plugin.

AnalogJS, founded and maintained by Brandon Roberts, solves this by doing exactly that. It fully decouples Angular from the CLI's build pipeline and exposes it as a standard Vite plugin. Just activate it, and these modern tools can suddenly compile and serve Angular components out of the box without any Angular-specific configuration. It just works.

// Detect dark theme var iframe = document.getElementById('tweet-2067695792106705118-982'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=2067695792106705118&theme=dark" }

ng-conf is ending

ng-conf is ending.

ng-conf was the first Angular conference, going back to 2014 with AngularJS, and it continued through to the modern Angular era all the way through 2025. This also means that there is no US-based Angular conference anymore.

In its place, a new conference called AI Dev Craft will debut in October in Las Vegas, with a call for speakers open.

// Detect dark theme var iframe = document.getElementById('tweet-2071616309742453054-891'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=2071616309742453054&theme=dark" }

Announcing spartan/ui 1.0

Robin Goetz — Wed, 24 Jun 2026 00:24:58 +0000

After a long and deliberate alpha, spartan/ui is now 1.0.

We shipped the first 30 primitives in August 2023 with a simple bet: building accessible, good-looking UI in Angular is harder than it should be, and the community deserved a better starting point. Almost three years later, that bet has grown into a stable, production-ready library of more than 55 components - built on signals, ready for zoneless, and server-side-rendering compatible out of the box.

Here's what 1.0 actually means.

Stable, and ready to build on

We stayed in alpha for a long time on purpose. It let us refine the APIs in the open, with real applications putting real pressure on the design, instead of freezing a v1 we'd regret six months later.

That patience is what 1.0 cashes in. The APIs are now stable and semantically versioned, so you can depend on spartan/ui/brain and upgrade with confidence. The copy-in spartan/ui/helm layer stays exactly as it's always been - yours to own, read, and customize. No black boxes, no fighting the library to change a style.

Built for modern Angular

Every primitive is built on Angular signals and standalone components. spartan is zoneless-ready and SSR compatible out of the box, so it drops cleanly into how Angular apps are actually written today - no extra setup, no adapters.

The split that's defined spartan from day one still holds. spartan/ui/brain carries the hard, unglamorous parts - ARIA, keyboard navigation, focus management - and keeps them maintained so you don't have to. spartan/ui/helm gives you full styling control on top, copied into your project like a recipe. Accessibility you can rely on; appearance you fully own.

From 30 primitives to 55+

The alpha shipped with 30 components. 1.0 ships with more than 55 - nearly double - including many of the most-requested additions over the past two years:

Data Table - sorting, filtering, and selection, the piece people asked for most
Sidebar - composable app navigation
Calendar and Date Picker
Carousel, Autocomplete, Pagination, and Breadcrumb

And we added Blocks: ready-made, fully responsive layouts assembled from spartan components - authentication pages, sidebar layouts, and multi-step steppers you can drop in and adapt. Less scaffolding, more shipping.

You can browse the full component set and the blocks.

This was built by a community

I want to be clear about something: spartan/ui is not a one-person project, and 1.0 least of all. It exists because a group of people kept showing up - reviewing PRs, building components, fixing the edge cases nobody sees, and arguing about API design until we got it right.

A huge thank you to the people who carried the heaviest load getting us here - Merlin (@MerlinMoos), Marc (@marcjulian), Ashley (@ashley-hunter), Sammy (@thatsamsonkid), Benni (@elite-benni), and Toni (@toniskobic) - and to every single person who has opened an issue, sent a PR, answered a question in Discord, or sponsored the work. There are too many of you to name, and that's exactly the point. spartan is what it is because of you.

If you've contributed and want to say hi or get more involved, the door is open in Discord.

Powered by Zerops

spartan's development infrastructure runs on Zerops, and has for a long time. Preview environments, the docs and demo site, the day-to-day plumbing that makes maintaining an open-source library of this size sustainable - Zerops powers all of it. Their support is a real reason we were able to keep iterating in the open without the infrastructure becoming a tax on the team. Thank you.

Get started

There's never been a better time to start.

Get started with spartan/ui →

spartan is MIT-licensed and built in the open. If it saves you time, consider sponsoring its development - sponsorships fund ongoing maintenance, new components, and keeping spartan free for the whole Angular community.

Here's to 1.0 - and to everything we build on top of it next.

Ng-News 26/15: Angular 22

ng-news — Tue, 23 Jun 2026 19:13:29 +0000

Angular 22 stable resources and Signal Forms are the headline topics, together with new dependency injection APIs such as @Service and injectAsync. Also in brief: debounced(), Vitest migration support, ChangeDetectionStrategy.Eager, WebMCP, community write-ups, and the ng-neat recovery.

Stable resources and Signal Forms

Angular 22 is out. Probably the most outstanding feature is the stabilization of the resource and the Signal Forms. There's much more but let's start with these two.

Resources, that are three functions resource(), rxResource() and httpResource(), have been introduced during Angular 19. There were some significant changes in Angular 20, and then in Angular 21 we got the snapshot feature. Resources have been experimental all the time, and after almost 1.5 years, they leave experimental status and become stable.

Similar story for Signal Forms, but at a just faster pace. They were introduced in 21 and are now also stable, so no developer preview either.

So in some way, these are features we already knew and some of us were already using quite successfully.

And let's not forget, also @angular/aria, the headless design system also became stable.

blog.angular.dev

What's new in Angular 22.0? - Ninja Squad

Angular 22.0 is out!

blog.ninja-squad.com

`@Service`, `injectAsync`, and `debounced()`

But, there are new features as well.

For one, we have the @Service decorator. That means it is on one side a shortcut for @Injectable({ providedIn: 'root' }) and on the other prevents using dependency injection via the constructor. Instead of constructor-based DI, you should go with the inject function and there is a dedicated migration available (ng generate @angular/core:inject).

@Service()
export default class NewsletterClient {
  private httpClient = inject(HttpClient);

  send(email: string): Observable<boolean> {
    return this.httpClient.post<boolean>(
      'http://some.host.com/newsletter/subscribe',
      { email },
    );
  }
}

Another feature for dependency injection is the asynchronous injector. So the value returned by injectAsync is not the service instance itself - you call it when you need the service and await the result. Why do we need it? Well, same thing why we do lazy loading in the router. We only want to load when it is actually needed.

export class NewsletterPage {
  private readonly newsletterModel = signal({ email: '' });
  private readonly newsletterClient = injectAsync(
    () => import('./newsletter-client'),
  );

  protected readonly newsletterForm = form(
    this.newsletterModel,
    (path) => { },
    {
      submission: {
        action: async () => {
          const client = await this.newsletterClient();
          client.send(this.newsletterModel().email)
        },
      },
    },
  );
}

So you won't use injectAsync when you need the service immediately but more when a user clicks on something or some later events. The service needs to be providedIn: 'root'. So it's best if you already apply the new @Service decorator.

And we have a debounced function. You give it a signal and a debounce time, and you are getting back a resource. Debouncing means, when the signal's value changes, the value in the derived resource would wait for the defined period of time until a new value comes. If that's not the case, then the resource will take on that value, and if not, the debouncing starts again.

As every Signal has an initial value, the debouncing for the first value doesn't happen.

@Component({
  selector: 'app-debounced',
  template: `Value {{ debouncedCounter.value() }}`,
})
export class DebouncedPage {
  protected readonly counter = signal(1);

  protected readonly debouncedCounter = debounced(this.counter, 600);

  constructor() {
    setTimeout(() => this.counter.update((v) => v + 1), 500);
    setTimeout(() => this.counter.update((v) => v + 1), 1_000);
    setTimeout(() => this.counter.update((v) => v + 1), 1_500);

    effect(() => {
      console.log(`value updated ${this.debouncedCounter.value()}`);
    });
  }
}

debounced() is experimental. @Service and injectAsync are not.

angular.love

Angular 22: The Most Important New Features at a Glance - ANGULARarchitects

Angular 22 stabilizes the Resource API and Signal Forms, makes OnPush the default change detection strategy, and brings @Service, injectAsync, debounced, as well as numerous template and router improvements. This article shows the relevant updates using concrete examples.

angulararchitects.io

Vitest and change detection

In Angular 21, we've received Vitest as the new default testing framework. It was not possible to easily migrate because a lot of us were using fakeAsync or waitForAsync to manage asynchronous tasks in tests. With Angular 22, that is possible again, but remember, fakeAsync and waitForAsync depend on zone.js. So if you have plans to move to zoneless or are already there, it is not an option.

If you run ng update, your components which are not OnPush will get a ChangeDetectionStrategy.Eager. That's the new alias for the old Default value, because default is not OnPush. Speaking of zoneless, if you want to migrate, staying with zone.js and moving all your components to OnPush as an intermediate step is a good approach.

blog.angular.dev

WebMCP

Also in terms of AI, there is experimental support for WebMCP. That means an agent can connect to your web application and can execute certain tool calls. That means, you in Angular have to expose calls to services with a description and so on, and then if the browser supports it, the agent can call them. So it is not necessary anymore that the browser has to read and interact with the DOM.

WebMCP is still in development, but we can expect to hear more from it in the future. There is also a feature which sets up forms for WebMCP.

Community content

As always, there is a lot of community content out there. We had a release video, a release blog and Mark Thompson, Angular's DevRel, was also guest at the Angular Plus Show.

For this episode, we additionally used the blogs from Cedric Exbrayat from Ninja Squad, Manfred Steyer from Angular Architects, and Mateusz Stefańczyk from House of Angular.

What's new in Angular 22.0? - Ninja Squad

Angular 22.0 is out!

blog.ninja-squad.com

angular.love

Angular 22: The Most Important New Features at a Glance - ANGULARarchitects

angulararchitects.io

ng-neat GitHub

Last but not least, a very important information. Last weekend, the popular ng-neat organization was removed from GitHub. That contained widely used libraries, like Elf for state management and Spectator for testing. Before that, members of the organization were also removed. At the moment, we don't know why because there was no official communication from the owner.

What is important though, that most of the libraries have been recovered and found their way back to GitHub under a new organization called ngneat-archive. We will keep you updated on this topic.

Reddit thread

Angular Addicts #50: Angular 22, Agentic Angular, Deploying to the Cloud & more

Gergely Szerovay — Tue, 16 Jun 2026 08:06:43 +0000

👋Hey fellow Angular Addict

This is the 50th issue of the Angular Addicts Newsletter, a monthly collection of carefully selected Angular resources that caught my attention. (Here are the 49th, 48th and 47th)

📢 Release announcements

📢 What's new in Angular 22.0?

By Cédric Exbrayat

💎Angular Gems of May, 2026

📰 Road to Angular 22: Debounce Signal

By Davide Passafaro

📰 Angular 22: Embracing the Signal-First Era

By Marco Martorana

📰 Modern Angular: Replacing Lifecycle Hooks with Signals

By Alain Chautard

📰 Scalable Angular Frontend Architecture with Nx Monorepos

By Fanis Prodromou

📰 Agentic Engineering: Which LLM Is Best for Angular Development?

By Alexander Thalhammer

📰 From Module Federation to Web Components: The Angular Migration Nobody Warned Me About

By Michael Seemann

📰 My Favorite AI Tools for Building Angular Apps

By Preston Lamb

📰 Build a Streaming Gemini Chat in Angular with Signals — Then Ship It on Cloud Run

By Tomasz Flis

📰 Deploying Angular applications to Cloudflare with Void

By Brandon Roberts

📰 How I Made My A2UI Dashboard 300 Times Faster

This article is part of Manfred Steyer's Agentic Angular series:

👨‍💻About the author

Follow me on Substack (Angular Addicts), Substack (AIBoosted.dev), Medium, Dev.to, Twitter or LinkedIn to learn more about Angular, and how to build AI apps with AI, Typescript, React and Angular!

🕹️Previous issues

If you missed the previous issues of the newsletter, you can read them here, these are the latest 3 issues:

📨 Submit your Angular resource

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

ng-news — Tue, 02 Jun 2026 20:55:34 +0000

Angular 22 stabilization (resources, Signal Forms, @angular/aria) and compiler ABI stability across patch versions for micro frontends are the headline items this week. Also in brief: linkedSignal's set option and NgRx's reverted delegatedSignal, plus error boundaries from Google I/O.

Angular 22 stabilization

The release of Angular 22 is getting closer, and we are also getting more and more information about the changes but also what awaits us beyond Angular 22.

We already know that Angular 22 will make a lot of features stable. That is resources, Signal Forms, but also @angular/aria. Stable means no breaking changes within majors.

Versioning and releases • Angular

The web development framework for building modern apps.

angular.dev

Compiler ABI and micro frontends

Another feature was announced, and it will be a happy message for anyone who's using micro frontends via Native Federation or Module Federation. Until now, whenever you loaded another Angular application/micro frontend during runtime, you had to make sure that it has been compiled with exactly the same version as the host application.

Why? Because the compiled Angular code was never part of the public API and didn't follow semantic versioning, which means the Angular team could introduce breaking changes within patch versions.

That is going to change. Breaking changes within a major can still happen in minors, but not in patch versions.

docs: establish compiler abi stability across patch versions #68623

alxhub posted on May 07, 2026

Define the new policy that the compiler ABI (the internal runtime APIs called by compiler-generated code) is stable across patch versions within the same minor version. This update unblocks microfrontend use cases and safer sharing of the Angular runtime across independent builds.

View on GitHub

linkedSignal `set` and delegatedSignal

In former episodes, we've already touched upon the need for a new Signal type, which is like linkedSignal, that derives the value from another Signal, but is not writable. At the same time though, it should be possible to have an option to write back to the original Signal.

That feature exists already for Signal Forms under the name DeepSignal, but it is only internal. And because there is a need for it for us as well, NgRx, a state management library, was about to introduce that as delegatedSignal in NgRx 22, but it is not going to happen and the existing commit was reverted.

linkedSignal itself will get a set option, which allows you to write back to the original Signal. So in some way what the delegatedSignal would have done will be part of the linkedSignal itself.

The PR has a label for minor version, which means Angular 22.1. Last summer, the difference between 20.0 and 20.1 was around 6 weeks. Given that Angular 22 will be released in the week of June 3rd, that means we are looking at a release of mid-July.

feat(core): add custom set option to linkedSignal #68708

alxhub posted on May 13, 2026

Introduce a custom set option in linkedSignal options to allow overriding and customizing the default write-back behavior of writable signals. This lets developers route updates back to the source of truth (e.g., converting Fahrenheit back to Celsius) or perform other side effects like updating properties inside a parent signal.

Additionally, the custom callback receives the standard signal setter as its second parameter (rawSet) to allow direct internal mutation if desired.

TAG=agy CONV=addbb5c4-4233-49e8-b844-6f732d7d5c72

PR Checklist

Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://github.com/angular/angular/blob/main/contributing-docs/commit-message-guidelines.md
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] angular.dev application / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

View on GitHub

ngrx/platform#5157 — revert delegatedSignal (Angular linkedSignal set planned)

Ng-News 26/11: TypeScript 6, NgRx RFCs, delegatedSignal

Google I/O: error boundaries

Google's conference Google I/O also took place, and Mark Thompson, Angular DevRel, gave a talk where, among other things, he introduced an upcoming feature which is called error boundaries.

You can see it as an elegant try/catch block for the template. Similar to @defer you wrap parts of the template into @boundary and if an error occurs, the boundary will catch it and display a fallback. Mark also mentioned that there could be an option to define retry logic for the boundary.

That will also improve the DX with resources, which throw the error if you access its value.

It was the first time that we heard about this feature publicly. Mark said that they plan to make it available as developer preview in Q3 this year, which probably means Angular 23.

Angular Addicts #49: AnalogJS 2.5, Agentic Angular & more

Gergely Szerovay — Tue, 12 May 2026 07:11:31 +0000

👋Hey fellow Angular Addict

This is the 49th issue of the Angular Addicts Newsletter, a monthly collection of carefully selected Angular resources that caught my attention. (Here are the 48th, 47th and 46th)

📢 Release announcements

📢 AnalogJS 2.5: Runtime i18n, Fast Compilation Mode, Hierarchical Content, and more!

By Brandon Roberts

💎Angular Gems of April, 2026

📰 Asymmetry of Angular Inputs and Outputs

By Matthieu Riegler

📰 Migrate from Karma To Vitest

By Marcell Kiss

📰 AI Agents for Developers: Which Tool Works Best in Real Projects?

By Maja Hendzel

📰 Back from Baby Bonding: Agents, Building Blocks, and the Future of AI Engineering

By Devin Chasanoff

📰 Extending a Video with Angular, Veo 3.1 Lite, Firebase Cloud Functions, and Firebase Cloud Storage

By Connie Leung

📰 Custom Catalogs in A2UI: Your Own Components for AI-Generated UIs

This article is part of Manfred Steyer's Agentic Angular series:

📰 RxJS to Angular Signals: Patterns, Pitfalls, and Practical Tips

By Alain Chautard

👨‍💻About the author

Follow me on Substack (Angular Addicts), Substack (AIBoosted.dev), Medium, Dev.to, Twitter or LinkedIn to learn more about Angular, and how to build AI apps with AI, Typescript, React and Angular!

🕹️Previous issues

If you missed the previous issues of the newsletter, you can read them here, these are the latest 3 issues:

📨 Submit your Angular resource

Ng-News 26/13: @Service, Native Federation, Angular Feature Lifecycles

ng-news — Tue, 05 May 2026 18:13:29 +0000

Angular 22's proposed @Service decorator and the likely stabilization of the resource API family. Also in brief: Angular feature lifecycle stages, Native Federation v4 changes, and fresh Oxc Angular compiler benchmark context.

Angular 22 preview: `@Service` and resource APIs

The release of Angular 22 comes closer, and we are also getting more and more information about the changes.

For example, we will get a new decorator for services, which will also be called @Service. What's the difference compared with the existing @Injectable decorator?

By default, @Service will automatically provide the service in root, and you cannot use constructor-based dependency injection anymore, but have to go via the inject function.

And another PR, which is still open, says the resource family, including httpResource, but also rxResource, will leave the experimental stage and become stable. So the developer preview gets skipped. One also has to say that we have had the resource APIs for almost 1.5 years now, so it is more than time.

feat(core): introduce @Service decorator #68195

crisbeto posted on Apr 14, 2026

These changes introduce the new @Service decorator which is a more ergonomic alternative to @Injectable. The reason we're adding a new decorator is that @Injectable has been around since the beginning of Angular and it has a lot of baggage that adds unnecessary overhead for users that generally want to define a singleton service, available in their entire app. The key differences between @Service and @Injectable are:

@Service is providedIn: 'root' by default. You can opt into providing the service yourself by setting autoProvided: false on it.
@Service doesn't allow constructor-based injection, only the inject function.
@Service doesn't support the complex type signature of @Injectable (useClass, useValue etc.). Instead it supports a single factory function.

Example:

import {Service} from '@angular/core';
import {HttpClient} from '@angular/common/http';
import {AuthService} from './auth';

@Service()
export class PostService {
  private readonly httpClient = inject(HttpClient);
  private readonly authService = inject(AuthService);

  getUserPosts() {
    return this.httpClient.get('/api/posts/' + this.authService.userId);
  }
}

View on GitHub

refactor(core): promote `resource`, `rxResource` & `httpResource` to stable #68253

JeanMeche posted on Apr 16, 2026

The time has come.

Note: #67382 introduced a breaking change where you could notice some sublte timing change on how value is set when using rxResource or a stream on a resource

View on GitHub

Feature lifecycle stages in Angular

Alejandro Cuba Ruiz wrote on the ng-conf Medium publication about what he calls the five lifecycle stages of an Angular feature: experimental, developer preview, stable, deprecated, and removed. The article is not a secret internal document; it lines up with what we occasionally also hear from the Angular team.

Experimental means the API can move under minors or patches, so the author argues to keep it out of production and to experiment in isolation. Developer preview is "we like the design, show us real-world pain" - safer than experimental, still not semver-frozen. Stable is the contract: breaking changes belong in majors, with migrations when possible. Deprecated gives you the familiar two-major-version runway, and removed is the point where the code is actually gone.

He also mentions tooling outside the official docs, for example a "Can I Use Angular Features" grid from Gerome Grignon, which can be handy if you support more than one Angular version.

Next to experimental, developer preview, and stable, there are also the deprecation and removal stages that Alejandro also covers.

So quite a sound guide to help you decide if and when you want to use a certain feature.

The 5 lifecycle stages of an Angular feature

Versioning and releases • Angular

The web development framework for building modern apps.

angular.dev

Native Federation v4 updates

Native Federation is next to Module Federation one of the most used libraries when it comes to building microfrontends in Angular. Native Federation version 4 was released and brings a bunch of updates, whereas the most visible one is a website with a lot of documentation. The GitHub repository was also moved to a new organization, the code is now split into multiple repositories, and an orchestrator that manages the microfrontends takes or will take over the old runtime.

Native Federation — Micro Frontends with Web Standards

A browser-native implementation of Module Federation for building Micro Frontends using web standards like ESM and Import Maps.

native-federation.com

Oxc Angular compiler benchmarks and caveats

In a former episode of ng-news, we've already covered Void Zero's experiments on writing the Angular compiler in the Oxidation Compiler, which is built on Rust.

There is now an official article where they publish official numbers and also give some background information on their development process, which is of course heavily AI-based.

They describe on the order of two months of work, mainly with Claude Code and Codex, under the steering of experienced engineers - not "the model wrote a compiler overnight," but agents doing large-scale porting and review work once the architecture and guardrails exist.

The headline numbers are eye-catching: they report on the order of six times faster compiles than the Angular CLI.

As always, be careful with those numbers, but they could be reasonable. Especially since they omitted some heavy tasks like template type-checking. They also admit that the non-existing type-check is a significant performance booster.

The compiler is available as a Vite plugin, @oxc-angular/vite.

VoidZero also writes that the repository will not be maintained long term. In parallel, they note that the Angular team has its own experiments with Oxc.

How we made the Angular Compiler faster using AI | VoidZero

How VoidZero built the Oxc Angular Compiler, an AI-powered Angular compiler that achieves up to 20x faster code compiling speed.

    <div class="color-secondary fs-s flex items-center">
        <img
          alt="favicon"
          class="c-embed__favicon m-0 mr-2 radius-0"
          src="https://voidzero.dev/favicon.svg"
          loading="lazy" />
      voidzero.dev
    </div>
  </div>
</div>

voidzero-dev/oxc-angular-compiler

Angular Addicts #48: TypeScript 6, OnPush as default, AI tools & more

Gergely Szerovay — Thu, 16 Apr 2026 08:19:10 +0000

👋Hey fellow Angular Addict

This is the 48th issue of the Angular Addicts Newsletter, a monthly collection of carefully selected Angular resources that caught my attention. (Here are the 47th, 46th and 45th)

📢 Release announcements

📢 Announcing TypeScript 6.0 - TypeScript

By Daniel Rosenwasser

📢 AnalogJS 2.4: Vite 8, Vitest Snapshot Serializers, Astro v6 Support, and more!

By Brandon Roberts

📢 Signality 0.1 & 0.2 is out

By Vyacheslav Borodin

Signality is a comprehensive library of signal-first utilities for Angular. SSR-ready, type-safe, and designed for seamless reactive composition with DI-interop.

🎫 Win a free ticket to WebExpo Conf (Prague, Czechia, May 27-28, 2026)

WebExpo is a conference for developers, designers and anyone involved in creating digital products and services, now with AI talks in focus It’s my favorite conference I have ever been to, and just like last year, I’m a community partner of the event, so I can give away one free ticket to my followers!

➡️HOW TO WIN A TICKET?

To participate in the raffle, subscribe to Webexpo's newsletter: https://webexpo.net/webexpo-newsletter/.

Then please send a screenshot of your subscription to this email address: gergely.szerovay+we26@gmail.com with the following email subject: “WebExpo Angular Addicts Ticket”, and an answer to the question: "Which speaker are you most excited about?".

I will accept entries submitted to this email address before 26. April 2026, 23:59 CEST (Sunday).

Some conditions: the prize is a conference ticket, which provides the winner with access to the program of the conference days. Premium Workshops are not included in the conference ticket. The conference ticket is not transferable to someone else and there is no refund in case the winner doesn't arrive or cancel. Flight tickets or accommodation are not included in the conference ticket.

So these are the steps:

1️⃣ Subscribe to Webexpo's newsletter
2️⃣ Send me an email with the screenshot, and an answer to the question: "Which speaker are you most excited about?".

❗️Please check out the DATE & LOCATION first, and only participate in the contest if you’d surely attend the event! Thanks for your consideration! And please share this opportunity with your friends and network!

The winner will be randomly selected on 27. April 2026.
I’ll contact the winner via email, GOOD LUCK!

WebExpo 2026 Conference website: https://webexpo.net/

🏷️And if you want to purchase a ticket, use the code "ANGULAR26" at the checkout to get 50 EUR off.

🤖 Angular AI skills, tools and development

📰 Migrating to Nano Banana 2: Enhancing Your Angular Firebase AI App

By Connie Leung

📰 Local AI, Reactive Routing, and the Vitest Migration!

📰 SpecKit Companion

By Alfredo Perez

💎Angular Gems of March, 2026

📰 Angular Schematics Deep Dive — Part 2

By Sakthikumaran Navakumar

📰 Vitest's 4.1 New "Fast-Forward" Mode Skips Timer Delays Instantly

By Younes Jaaidi

📰 Migrating to Angular Signal Forms: Interop with Reactive Forms

By Manfred Steyer

📰 OnPush will become the default CD Strategy - What to expect?

By Enea Jahollari

📰 Angular Templates: Interpolation vs. property binding, what’s the difference?

By Alain Chautard

👨‍💻About the author

Follow me on Substack (Angular Addicts), Substack (AIBoosted.dev), Medium, Dev.to, Twitter or LinkedIn to learn more about Angular, and how to build AI apps with AI, Typescript, React and Angular!

🕹️Previous issues

If you missed the previous issues of the newsletter, you can read them here, these are the latest 3 issues:

📨 Submit your Angular resource

Ng-News 26/12: Future of Selectorless, Skills vs. MCP, Zoneless Testing

ng-news — Fri, 10 Apr 2026 13:22:25 +0000

Ng-News 26/12 covers the Angular Q&A on selectorless and Skills versus MCP, then zoneless testing and auto tick from the Angular Plus Show.

Angular Q&A: selectorless and Skills vs MCP

The monthly Q&A session featured Mark Thompson as host and Alex Rickabaugh, tech lead of the Angular framework.

Alex explained why selectorless got downgraded. Selectorless was a planned feature that would have allowed referring to components in a template by using their class name. In the latest roadmap update, that feature was removed.

According to Alex, selectorless would have been a huge jump. The risk of an AI agent not being able to write modern Angular code was not worth the DX benefits from selectorless. Therefore, that feature is on hold and will be re-evaluated in the future.

Timestamp: 0:05:50

Skills and MCPs: According to Alex, Skills are starting to replace MCP tools, because a Skill can tell the agent about certain CLI commands, which can replace a dedicated MCP tool call.

Timestamp: 23:11

Zoneless testing and auto tick

The Angular Plus Show published an episode on zoneless testing with Andrew Scott (Angular team), @younesjd, and Rainer Hahnekamp.

Zoneless tests run outside Zone.js, which clarifies some patterns but means you cannot use fakeAsync or waitForAsync in that mode.

With zoneless, change detection in tests would be triggered like in the application, whereas in zone-based tests, users had to trigger it very often manually via ComponentFixture#detectChanges.

The panel also discussed auto tick, recently released around the time of recording and covered in a prior ng-news segment.

It can simplify async behavior when timer APIs are faked, but it is not always the first choice: mixing real and fake timers produces confusing failures, and faking timers overrides timing globally and can affect third-party code you do not control.

Upcoming Conferences

This is a new feature of ng-news. At the end of each article, we are listing all upcoming conferences.

NG Belgrade Conf 2026

NG Belgrade Conf 2026 is the largest Angular conference in the Balkans. It takes place in Belgrade, Serbia, including a Conference Day on May 7th and a Workshop Day on May 8th. Join us to explore the latest trends and best practices in Angular!

angularbelgrade.org

ngbaguette.angulardevs.fr

Ng-News 26/11: TypeScript 6, NgRx RFCs delegatedSignal, Resource Extensions

ng-news — Fri, 03 Apr 2026 17:43:23 +0000

Main topics: TypeScript 6.0 and NgRx (RFCs for delegatedSignal and resource extensions). Also in brief: Martina Kraus on security, debounce for async validators, Alfredo Perez on SpecKit, and Angular Graz on YouTube.

TypeScript 6.0

TypeScript 6.0 was released and it is going to be the last TypeScript version, written in TypeScript. Officially, TypeScript 6 is seen as the bridge between TypeScript 5 and TypeScript 7 (which will be written in Go). First of all, TypeScript 6 is not yet part of Angular. So you can't make use of those changes yet. Angular 21 supports TypeScript 5.9, but 22 will support TypeScript 6.

In order to prepare for version 7, TypeScript 6 comes primarily with a lot of deprecations and new default settings, which pay tribute to the modern TypeScript ecosystem.

For example, ESM is now default module system, the strict mode is enabled and the target is the ECMAScript version with the number of the current last year. By now, that would be ECMAScript 2025.

When it comes to the deprecation. Target ES5, which was the last version of JavaScript without the class syntax, lambda expressions, Promises, let or const, string interpolation, and much more got deprecated.

What also went away is the baseUrl property in the tsconfig.json file, support for the module systems amd, umd, and systemjs (not sure if our younger colleagues still know what that is) has also gone. You can of course also revert those deprecations, but be aware that in TypeScript 7, that means game over.

There is an automatic migration tool available, which is marked as experimental.

Announcing TypeScript 6.0 - TypeScript

TypeScript 6.0 is now available! TypeScript 6 is a stepping-stone release, aligning with the upcoming native-speed 7.0 release.

devblogs.microsoft.com

There are also new features, and the most prominent one is the introduction of the Temporal API.

This is a new, built-in date and time API in JavaScript, which can be seen as a full replacement for the old Date object. As that, it provides way more functionality for example handling timezones, a calendar which can be used to reflect Chinese or other calendar systems, immutability and a range of utility functions.

Some veterans of us might remember the switch to the Date-time API in Java more than 10 years ago. It kind of did the same thing.

Temporal API has reached stage 4 of the TC39 process, which means it is standardized, finished. That doesn't mean that each platform supports it. The latest version of Chrome, Firefox supports it, but not Safari and also Node.js which means if you use it, you should secure your code with polyfills.

typescriptlang.org

const today = Temporal.Now.plainDateISO();
const startOfYear = today.with({ month: 1, day: 1 });
const diff = startOfYear.until(today);

console.log(`${diff.days} days have passed`);

NgRx RFCs

NgRx is the most used library for state management in Angular and official work has begun on supporting resources but also forms. Two RFCs for that have landed.

`delegatedSignal()`

The first RFC is related to supporting Signal Forms and it introduces a new Signal type called delegatedSignal. To the outside it is a writable Signal, but it doesn't store a value. Instead it writes and reads to another Signal. What's the use of it?

Let's say we have a user object in a Signal, that has two nested properties: name and address. name has firstName and lastName, and address has street and city, like this:

const user = signal({
  name: { firstName: 'John', lastName: 'Doe' },
  address: { street: '123 Main St', city: 'Anytown' }
});

If we have a form, which requires a flattened version of the user object, we would usually create a linkedSignal. The problem is that changes in the form might be synchronized back to the original Signal. At the moment, the only way would be to use an effect.

@Component({
  template: ``
})
export class UserPage {
  user = signal({
    name: {
      firstname: "John",
      lastname: "Doe"
    },
    address: {
      street: 'Main Street',
      city: 'London'
    }
  })

  userFormModel = linkedSignal(() => ({
    firstname: this.user().name.firstname,
    lastname: this.user().name.lastname,
    city: this.user().address.city,
    street: this.user().address.street,
  }))

  userForm = form(this.userFormModel);

  syncEffect = effect(() => {
    const { firstname, lastname, street, city } = this.userFormModel();

    this.user.set({
      name: { firstname, lastname },
      address: { street, city }
    })
  })
}

delegatedSignal solves this problem by writing synchronously back to the original Signal.

// PROTOTYPE!!!
export function delegatedSignal<T>(config: {
  computation: () => T,
  update: (value: T) => void
}
): WritableSignal<T> {
  const delegated = linkedSignal(config.computation);

  delegated.set = (value: T) => config.update(value);
  delegated.update = (updateFn: (value: T) => T) => updateFn(delegated())

  return delegated;
}


@Component({
  template: ``
})
export class UserPage {
  user = signal({
    name: {
      firstname: "John",
      lastname: "Doe"
    },
    address: {
      street: 'Main Street',
      city: 'London'
    }
  })

  userFormModel = delegatedSignal({
    computation: () => {
      const { 
        name: { firstname, lastname }, 
        address: { city, street } 
      } = this.user();
      return { firstname, lastname, street, city }
    },
    update: ({ firstname, lastname, street, city }) => {
      this.user.set({
        name: { firstname, lastname },
        address: { street, city }
      })

    }
  })

  userForm = form(this.userFormModel);
}

The delegatedSignal can be used for different use cases. Not just forms. Regarding the SignalStore, you could connect a Signal Form and a SignalStore together, where each change in the form is directly written to the SignalStore.

You can see the delegatedSignal as a linkedSignal which doesn't create a clone, but just writes directly back to the original Signal. delegatedSignal exists already in the Angular framework (slightly differently as deepSignal), but is not exposed publicly. Angular uses it for the Signal Forms:
https://github.com/angular/angular/blob/394ad0c2a26eec8a8f7136b1b7971420b30a117e/packages/forms/signals/src/util/deep_signal.ts#L21

ngrx/platform#5121 — RFC delegatedSignal

Resource Extensions

And the second RFC is related to resources. It allows to extend the resources which goes beyond the possibilities of the current snapshot function. For example, an extension would change the behavior of a resource in an error state, where an access to the value does not throw. Custom extensions are possible as well and there is even the option to define default extensions.

All two issues were created by @markostanimirovic and if the same Marko was also guest at a previous episode of the Angular Plus show. So if you are interested to hear more about state management and SignalStore specifically, you should check out the episode.

ngrx/platform#5126 — RFC resource extensions

Martina Kraus on security (Angular Plus Show)

In other news, the Angular Plus Show also had Martina Kraus as guest, which usually means the topic is about security.

Together with the three hosts, Lara Newsom, Brooke Avery, and Jan-Niklas Wortmann, they discussed a whole portfolio of security. Be it trusted types, Sanitization, attacks like XSS and CSRF, but also content policies and the increased risk that comes with AI.

At the end, Martina gave some tips where to start with security and she also highlighted the OWASP juice shop, which is written in Angular and is a playground to try out different vulnerabilities.

And by the way, you should not store your access token in local storage.

OWASP Juice Shop | OWASP Foundation

Probably the most modern and sophisticated insecure web application for security trainings, awareness demos and CTFs. Also great voluntary guinea pig for your security tools and DevSecOps pipelines!

owasp.org

Form validation: debouncing async validators

And we have a third debounce option in Angular. For Signal Forms, there is a debounce function, which debounces the synchronization of a form field with the underlying model. The second is a debounced function, scheduled for Angular 22 and is meant for any Signal type out there. The new one, is debouncing for asynchronous validators in Signal Forms. That allows you to have "undebounced" synchronous validators, but debouncing an asynchronous validator.

That feature has been merged into the 22 version branch, but didn't make it into the latest 21.2.7 version. So it seems, we have to wait for Angular 22.

angular/angular@24e52d4 — debounce on validateAsync / validateHttp

Alfredo Perez: SpecKit and SpecKit Companion

@alfredoperez published a three-article series about a Spec-driven development process with AI. The most prominent tool in that spectrum is GitHub's SpecKit, which Alfredo describes. Additionally, he has created a VSCode extension, called SpecKit Companion, not just to visualize but also to edit and execute that specification.

Since GitHub's SpecKit is not the only tool out there, Alfredo also shows alternatives and how SpecKit Companion can be configured to support those tools as well.

https://medium.com/ngconf/speckit-companion-e4fc99d1e061

https://medium.com/ngconf/custom-workflows-in-speckit-companion-266fda3b5eec

https://medium.com/ngconf/build-your-own-sdd-workflow-daa3fc1ae673

https://marketplace.visualstudio.com/items?itemName=alfredoperez.speckit-companion

Angular Graz Meetup videos

Finally, the recordings of the Angular Graz Meetup are available on YouTube. They are published not at once but in a regular interval.

DEV Community: Playful Programming Angular

Angular Addicts #51: spartan/ui 1.0, A2UI, Signal Debouncing & more

👋Hey fellow Angular Addict

📢 Release announcements

📢 Announcing spartan/ui 1.0

💎Angular Gems of June, 2026

📰 Agentic Engineering: How to Set Up Your Harness for Angular Development

📰 Getting to Know Angular Resource Snapshots

📰 Making the Context Across 46 Repositories Semantically Searchable for AI (Part 2)

📰 Demystifying A2UI: How to Make AI Agents “Speak UI” in Your App

📰 Angular resources are not a good fit for Guards

📰 Angular Material Theming System Course — Now 100% Free

📰 TanStack Query style caching, the Angular-native way

📰 Architecture Beyond Layers: tsarch for AI Coding Agents

📰 AI Made Coding Faster, But My Day Harder to End | Chau Tran

📰 How to Debounce Angular Signals?

📰 7 New JavaScript Features (And 2 I'm Still Waiting For)

👨‍💻About the author

🕹️Previous issues

📨 Submit your Angular resource

Ng-News 26/17: PrimeNG's New Licensing, and A2UI for Angular

Future of PrimeNG

A2UI

routerResource

Micro-Frontends

Ng-News 26/16: OpenNG Foundation, spartan/ui

OpenNG Foundation

spartan/ui 1.0

AnalogJS in Storybook

ng-conf is ending

Announcing spartan/ui 1.0

Stable, and ready to build on

Built for modern Angular

From 30 primitives to 55+

This was built by a community

Powered by Zerops

Get started

Ng-News 26/15: Angular 22

Stable resources and Signal Forms

@Service, injectAsync, and debounced()

Vitest and change detection

WebMCP

Community content

ng-neat GitHub

Angular Addicts #50: Angular 22, Agentic Angular, Deploying to the Cloud & more

👋Hey fellow Angular Addict

📢 Release announcements

📢 What's new in Angular 22.0?

💎Angular Gems of May, 2026

📰 Road to Angular 22: Debounce Signal

📰 Angular 22: Embracing the Signal-First Era

📰 Modern Angular: Replacing Lifecycle Hooks with Signals

📰 Scalable Angular Frontend Architecture with Nx Monorepos

📰 Agentic Engineering: Which LLM Is Best for Angular Development?

📰 From Module Federation to Web Components: The Angular Migration Nobody Warned Me About

📰 My Favorite AI Tools for Building Angular Apps

📰 Build a Streaming Gemini Chat in Angular with Signals — Then Ship It on Cloud Run

📰 Deploying Angular applications to Cloudflare with Void

📰 How I Made My A2UI Dashboard 300 Times Faster

👨‍💻About the author

🕹️Previous issues

📨 Submit your Angular resource

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

Angular 22 stabilization

Compiler ABI and micro frontends

linkedSignal set and delegatedSignal

PR Checklist

PR Type

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

Other information

Google I/O: error boundaries

Angular Addicts #49: AnalogJS 2.5, Agentic Angular & more

👋Hey fellow Angular Addict

📢 Release announcements

📢 AnalogJS 2.5: Runtime i18n, Fast Compilation Mode, Hierarchical Content, and more!

💎Angular Gems of April, 2026

📰 Asymmetry of Angular Inputs and Outputs

📰 Migrate from Karma To Vitest

`@Service`, `injectAsync`, and `debounced()`

linkedSignal `set` and delegatedSignal

Angular 22 preview: `@Service` and resource APIs

`delegatedSignal()`