SignalForms are now available in Angular’s main branch for early adopters. Meanwhile, the community pushes forward with mutation support, and Angular recaps its summer progress. Plenty to catch up.
✅ SignalForms now in main!
SignalForms have officially been merged into the main branch! And since Wednesday, there’s even a release of Angular tagged with next (not latest) that includes the new SignalForms.
That means: for very enthusiastic developers, you can already try it out - even though it's still in pre-experimental status. Don’t expect everything to work perfectly just yet. APIs may change quickly, bugs will be fixed, and documentation will follow.
But if you want to be on the bleeding edge: Go for it!
🎙 Angular Q&A with Mark & Jeremy
Last week, we also had the Angular Q&A session, as usual with Mark Thompson and Jeremy Elbourn from the Angular team.
As expected, SignalForms were a topic. There was a question about the future of Reactive Forms, and Jeremy mentioned that - in the long run - SignalForms are meant to replace both Reactive and Template-driven forms.
But as always, that doesn’t mean they’ll be removed - so there’s no need to rewrite your existing form-specific code.
Time position: 5:45
The majority of the session was about Zoneless.
When asked what architectural changes that brings, Jeremy explained that developers now need to be more aware of what state is changing.
If you’re using Signals, that’s Angular’s native representation of state, and it just works.
If you don't use Signals, it still works, but is not that easy.
Time position: 49:30
Jeremy also gave a brief update on the broader vision for modern Angular - including:
- Selectorless components
- Signal components (no lifecycle hooks)
- New authoring format
- Native TypeScript in templates
They are working towards this vision, but there’s no specific timeline yet.
Time position: 1:04:20
At the very end, Mark also announced another live stream, scheduled for September 16.
It’s called "Explore the world of possibilities" and will focus on Angular and AI.
🛠 Community Mutations for SignalStore
Disclaimer: There’s a rule in ng-news that forbids self-promotion, but sometimes there are exceptions — especially when there's a whole team involved.
That being said, ngrx-toolkit is a library that provides a set of custom extensions for the NgRx SignalStore.
The most popular one is probably the support for Redux DevTools.
Now, by the initiative of Manfred Steyer — who, like me, is a member of the NgRx Toolkit team — we’ve introduced a mutation feature that can even be used without SignalStore.
"Mutations" is the term the Angular team often uses to describe the opposite of resources, namely when we want update state on the server.
Right now, mutations are not a priority for the Angular team since they’re focused on Signal Forms.
But for some of us who already want to go all-in on Signals, mutations are essential — and now, a community version is available.
With mutations, you define a POST, PUT, or DELETE HTTP command, which can then be invoked.
The ngrx-toolkit version handles race conditions and exposes status information — both per mutation and globally. The exposed meta-data is quite similar what we already find in the resource.
So if you’re looking to adopt a mutation mindset, this is one way forward.
Of course, keep in mind that an official mutation solution might still come eventually — but probably not very soon.
ngrx-toolkit.angulararchitects.io
To be fair, this isn’t the first community implementation.
There have been others — for example:
- Angular Query
- CRUDResource by Tomas Trajan
- GraphQL clients with built-in mutation support
🤫 The Hidden Costs of Updating Angular
It’s very often said that updating Angular is rather easy — you just run ng update and that’s it.
But one of the main challenges is updating third-party libraries. There’s always the risk that they lag behind or aren't maintained anymore.
This exact topic — the hidden costs of updating Angular — was the focus of last week's Angular Space Podcast, with host Armen Vardanyan and guest Gerome Grignon.
🛑 Analog.js Drops Support for the ng Format
Analog.js, a meta-framework for Angular, has dropped its support for the ng format.
A little bit of context: the ng format was an alternative syntax for writing components — one that focused purely on the template and avoided using classes.
At its introduction, it caused quite a bit of disturbance in the community.
Later on, the Angular team mentioned that they are internally experimenting with similar formats, and it could very well be that one of these formats eventually makes it out of those internal experiments.
fix(vite-plugin-angular): remove support for Analog SFCs
#1867
☀️ Angular Summer Recap & Nx Postmortem
Finally, the Angular team published a summary of all the new features they landed over the summer. It’s a great overview if you want to catch up on everything that happened in recent months.
Angular Summer Update 2025. Authors: Jens Kuehlers Mark Techson | by Angular | Aug, 2025 | Angular Blog
Authors: Jens Kuehlers Mark Techson
blog.angular.dev
Nx, an alternative to the Angular CLI, also published their postmortem about the recent incident — which I covered in the last episode.
During the attack malicious package were published and the Postmortem explains the incident quite in detail.
S1ngularity - What Happened, How We Responded, What We Learned | Nx Blog
Malicious Nx packages were published to npm via GitHub Actions exploit. Learn what happened and how we enhanced security measures.
nx.dev
Top comments (0)