angular.love

Meme of the month from our last newsletter 😂 → Follow the #Angular Recap newsletter on LinkedIn → Or sign up for our e-mail newsletter on our blog to receive fresh #AngularNews even quicker! buff.ly/Z5LMwUi ⏰

In our pre-release poll for the new edition of “The Ultimate Guide to Angular Evolution,” we asked which area of #Angular22 matters most to you ❓ The results are in, and after a close race, performance took the top spot 👇 Here’s how #Angular v22 rises to the challenge: 🧹 Route injector cleanup (experimental) Frees memory by removing unused route injectors. 🛠️ OnPush by default Cuts unnecessary change detection. 💧 Incremental hydration by default Improves SSR performance with less setup. ⚙️ #SSR resource caching Prevents duplicate data fetching after hydration. 🐢 Lazy service injection Loads heavy services only when needed. Explore these Angular v22 performance improvements in the new edition of the ebook, and use Smart Tags to quickly find what matters most to you! Download here → buff.ly/Yk7OUli

Does your team use AI? However, everyone feels like no shared process, no real guidelines, just... vibes? 👨‍💻 🌊 You're not alone. Most dev teams have adopted Copilot, Cursor, and Claude individually, without ever deciding as a team how to actually use them. -> more code, not necessarily better delivery, and many unclear expectations around AI in code review. This is usually a leadership gap, which is why House of Angular's CTO, Greg Lipke, is running a free session specifically for the people who can actually fix it: "How to Implement and Control AI in Your Dev Team" ⭐️ Free register: buff.ly/0Bm9xrP for CTOs, Tech Leads, and Heads of Engineering. 📅 August 5 | 3 PM CEST | Online | Free If that's you, register below. If it's not, but you know exactly who on your team it is, this might be worth forwarding. Fixing the chaos benefits everyone stuck reviewing AI-generated PRs at 5 PM on a Friday. 😅

Forget “#AI will replace developers.” Forget “ignore AI, it’s overhyped.” Here’s how Angular GDEs actually use it in 2026 ⬇️ In the latest version of “The Ultimate Guide to #Angular Evolution,” we asked Google Developer Experts and top Angular pros how they use AI in their daily workflows. 🤖 The result is a brand-new, AI-focused chapter available exclusively in the latest ebook edition. Below, there is a raw, honest snapshot of where we are right now And because AI evolves rapidly, we’ll continue updating this section in future editions of the ebook. → If you want a trusted, grounded signal instead of the usual hype, this chapter is a must-read for your #DevEx. 📚 Read the full expert section in the free ebook: buff.ly/3yMAXbR

👉 youtube.com/watch?v=DKNUAP…

Still haven’t fully caught up with zoneless #Angular? This is your sign to fix that 👇 Zone.js powered Angular change detection for years, but now #ModernAngular is shifting to a model with greater predictability and performance control. And if you’re not 100% sure what that means in practice, this talk is a great place to start. → During Angular Spring Camp 2026, @skorupka_k, #AngularArchitect & Team Leader at @HouseOfAngular, walked through: ✅ How Angular’s change detection has evolved ✅ What zoneless mode actually changes ✅ What performance wins it brings The full talk: “Zoneless Angular: Predictable Performance” is now available to watch on our YouTube channel. 🎬 Link below!

"The Ultimate Guide to #Angular Evolution," covering v22 + AI in Angular, is officially OUT! 🥳👇 After >6,200 downloads of our previous editions, we’re back with something even bigger 👀 This time, we added a brand-new section dedicated entirely to #AI, too! 🤖 Here is what’s waiting for you inside: 🆕 #Angular22 Chapter [NEW]: Every major change broken down into a practical problem → solution → benefit structure. 🛠️ #Code Snippets: Real examples you can copy-paste straight into your project. 🏷️ Smart Tags: Every feature is tagged by Performance, #DX, #UX, or Efficiency. Skip straight to what you need. 🔥 AI in Angular Section [NEW]: A brand-new, honest snapshot of how GDEs actually use AI in their daily workflows today. Thanks for sharing your invaluable insights: @prodromouf, @m_stefanczyk, @GeromeDEV, @AlainChautard, @puppo92, @webdave_de, @DecodedFrontend, @fati_amzil, @connieleung404, @StefanvHaas, @rainerhahnekamp, @MarkoStDev 🎁 Bonus package: We’ve prepared a few extras only for our readers to help you and your team implement the updates. Check your inbox after downloading the ebook. 📖 Download your copy here: buff.ly/3yMAXbR

🔗tiny.pl/cfzwf5zkp

When moving away from complex #RxJS streams, there’s usually one problem devs face 👇 Keeping the previous value when the reactive source changes. Why is it important to keep it? ⚙️ Because it gives you more control over loading states, skeleton views, and #UI flickering. Luckily, #Angular Resource Snapshots can help with exactly that, and #GDE @prodromouf just published a new article on this exact topic 🔥 Inside: → skeleton loader and loading indicator → what exactly ResourceSnapshot is → Displaying loading indicator and error banners while retaining the values ➕ visual walkthroughs that help illustrate the topic A practical must-read if you want smoother Angular UIs! Read under the link in the comments ↓

#Angular22 covers a lot of ground. Which area matters most to you? 👇 In “The Ultimate Guide to #Angular Evolution,” we used these 4 categories to tag features. Now, we want to hear what you care about most! 💬 Vote in the comments. Results will be shared soon, showing how v22 addresses the top choice.

🆕 #Angular22: Integration of WebMCP Starting in #Chrome 149, the proposed #WebMCP API officially enters its origin trial. This standard lets you expose structured tools (like JS functions and HTML forms) directly to browser-based AI agents, so they know exactly how to interact with your application. → #Angular 22 already provides experimental, framework-level support for this new API across several areas: 📱 Application-wide: Use provideExperimentalWebMcpTools() in your app.config.ts to register global tools. 🧭 Route-scoped: Define provideExperimentalWebMcpTools() at the route level and pair it with withExperimentalAutoCleanupInjectors() to ensure tools are automatically unregistered when the user navigates away. 💻 Service-scoped: Call declareExperimentalWebMcpTool() inside a service constructor to make the tool available strictly during that service's lifecycle. 📝 Form-scoped: Pass the experimentalWebMcpTool property into your Signal Form options to define a form-specific WebMCP tool. Currently, there is no support for traditional Reactive Forms. Below, there’s an example of an application-wide WebMCP that allows agents to navigate across pages in the application 👇 A general recommendation is to make sure to validate agent inputs at runtime, as the Angular API does not provide built-in schema guards! For more information about this new API, see the official documentation.

🎥 youtube.com/watch?v=JJBzto…

Signal Forms are stable! Now you have no excuse not to catch up on them 😎👇 And we’ve got the perfect opportunity for you to do that. → During Angular Spring Camp 2026, #GDE @m_stefanczyk took the stage to dive deep into this game-changing feature: ✅ How to fix the typing and template issues of traditional Reactive Forms. ✅ How to build your first #Angular Signal Form. ✅ The right way to handle async validation. ✅ How to manage arrays seamlessly without ever touching FormArray. And much more. The full talk is now available to watch on our YouTube channel. 🎬 Link in the comments below!

Exciting news: a new version of your favorite #Angular ebook is brewing! ☕ → "The Ultimate Guide to Angular Evolution" is coming with #Angular22, and it’s better than ever! 👇 🤖 For this edition (knowing how much #AI noise surrounds us now), we created a special chapter about AI in Angular, with opinions and insights from top Angular experts! We are finalizing the text right now, but we want to hear from you first: 💬 How are you using AI in your Angular projects today? Let’s talk below!

🔥 New in #Angular: Custom set Option for linkedSignal Sometimes, you may want the set and update operations of a linkedSignal to write back to the source of truth instead of updating the linkedSignal's value directly. This is exactly where the new feature comes in handy: custom set function within the linkedSignal options. → The community is already calling this feature a game-changer for integrating #SignalForms with Stores from @ ngrx/signals library. ⌛ Previously: if you wanted a reactive form to immediately write user input back to a store, you had to manually wire up clunky effects. ⚡ Now: linkedSignal acts as a clean bridge: your form gets the writable signal it needs, and the custom set function handles synchronously dispatching those updates right back to the store.

Here’s an example use case and a link to the PR. Feel free to share your thoughts github.com/angular/angula…

#Angular: Optional Initial Value for Signals - Proposal 🚦 We need your feedback! Drop your vote in the poll below: Should Angular allow signal() to be called without an initial value? 👇 → How many times have you had to explicitly type signal(undefined) just because you didn't have an initial value to provide? It feels like something that should work out of the box. A new PR in the Angular #repository from our very own blog contributor Artur Androsovych proposes adding a no-argument overload to signal(). ⚙️ This change allows the signal to automatically infer undefined when no initial value is passed, matching the exact behavior we already have with the input() API. Instead of the verbose typing, you could simply write: name = signal(); The Angular core team was initially hesitant to implement this feature due to a lack of clear demand. Is this something you would use on a daily basis? 👀 Review the example in the comment and let us know your thoughts in the poll below!

Should Angular allow signal() to be called without an initial value?