The Angular team has landed SignalForms in the main branch, opening the door for early experimentation. In parallel, the community is advancing mutation capabilities, and a summer recap highlights what the framework has accomplished. There’s a lot to digest here.
✅ SignalForms now in main!
The SignalForms code has officially landed in the main branch. As of Wednesday, a new Angular release tagged as next (rather than latest) is available, and it comes bundled with SignalForms.
This means adventurous folks can start experimenting immediately—though the feature remains in a pre-experimental phase. Don't hold your breath for a polished experience yet. Expect frequent API changes, ongoing bug fixes, and documentation that’s still being written.
Still, if you’re eager to live on the cutting edge—have at it!
🎙 Angular Q&A with Mark & Jeremy
Angular hosted its usual Q&A session last week, featuring Mark Thompson and Jeremy Elbourn.
SignalForms came up, naturally, with a query about Reactive Forms’ fate. Jeremy indicated that, over time, SignalForms are designed to take over from both Reactive and Template-driven forms.
Still, as always, that doesn’t signal removal — so there’s no urgency to migrate your existing form code.
Timestamp: 5:45
Zoneless took up the bulk of the discussion.
Asked about its architectural implications, Jeremy pointed out that developers must now track which state changes more carefully.
With Signals, state is Angular’s native representation, and everything runs smoothly.
Without Signals, functionality remains, but it’s not as straightforward.
Timestamp: 49:30
Jeremy also shared an overview of the longer-term roadmap for modern Angular, which covers:
- Selectorless components
- Signal components (no lifecycle hooks)
- A new authoring format
- Native TypeScript support in templates
They’re pushing toward this roadmap, though no exact dates are set yet.
Timestamp: 1:04:20
To wrap up, Mark revealed another livestream scheduled for September 16.
Titled "Explore the world of possibilities," it’s centered on Angular and AI.
🛠 Community Mutations for SignalStore
A quick note before diving in: ng-news typically steers clear of self-promotion, yet every now and then, an exception is warranted—particularly when a collective effort is behind it.
With that out of the way, ngrx-toolkit offers a suite of bespoke extensions for the NgRx SignalStore.
Its standout feature is arguably the Redux DevTools integration.
Driven by Manfred Steyer—a fellow teammate on the NgRx Toolkit project—we've rolled out a mutation capability that works standalone, needing no SignalStore at all.
In Angular's parlance, "mutations" refer to the counterpart of resources: operations to synchronize state changes with a server.
At present, the Angular team isn't prioritizing mutations, as their focus is on Signal Forms.
However, for those eager to embrace Signals fully, mutations are indispensable—and a community-driven version now fills that gap.
This approach involves declaring an HTTP action—whether POST, PUT, or DELETE—that you can trigger on demand.
The ngrx-toolkit implementation tackles race conditions and surfaces status details, covering both individual operations and the overall picture. The metadata offered aligns closely with the resource API's structure.
If a mutation-centric workflow appeals to you, this offers a viable path forward.
Just remember, an official solution may arrive in the future—just not in the immediate horizon.
ngrx-toolkit.angulararchitects.io
It’s worth noting that this isn’t the first time the community has built something like this.
Several other solutions already exist, including:
- Angular Query
- CRUDResource by Tomas Trajan
- GraphQL clients offering native mutation capabilities
🤫 The Hidden Costs of Updating Angular
People frequently claim that updating Angular is straightforward — just invoke ng update and you’re done.
Yet managing third-party libraries remains a significant hurdle. They may fall behind or become unmaintained, and that risk is always present.
Last week’s Angular Space Podcast explored this very issue — the hidden costs of upgrading Angular — featuring host Armen Vardanyan alongside guest Gerome Grignon.
🛑 Analog.js Drops Support for the ng Format
Support for the ng format has been removed from Analog.js, the Angular meta-framework.
To give you some background: the ng format represented an alternate way of authoring components, concentrating solely on the template and steering clear of classes.
When it first appeared, it stirred up considerable controversy within the community.
Subsequently, the Angular team noted that they are exploring comparable formats internally, and there is a real chance one of these approaches emerges from those internal efforts down the line.
fix(vite-plugin-angular): remove support for Analog SFCs
#1867
☀️ Angular Summer Recap & Nx Postmortem
The Angular team has at last shared a recap of the features introduced during the summer. If you are trying to get up to speed on all the happenings of the last few months, this offers a solid starting point.
Nx, which serves as an alternative to the Angular CLI, released its own postmortem on the recent incident that I discussed in the previous episode.
Malicious packages had been published during the attack, and the postmortem provides a fairly thorough breakdown of what happened.
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