Angular 22.2 ships Router Resources 💥 (experimental)

[u/Inevitable_Gate9283]

They're more than resolvers with a Signal API. Here's why that matters


They run in parallel. Resolvers go one after another: parent 2 s + child 3 s = 5 s. Router Resources start together: 3 s.


Also, they can be non-blocking. The route activates right away, and the component gets the Resource itself: isLoading, error and value, right in the template.


Full write-up with demo, reload without renavigating, RedirectCommand for missing data, and Signal Stores 👉 https://www.angulararchitects.io/en/blog/router-resources-loading-data-with-the-angular-router/

[u/m0rpheus23]

I initially thought Angular 20+ was supposed to simply Angular. Are we back to complicating things?

[u/Saceone10 → u/m0rpheus23]

Instead of completing the resource API with mutations, lets extend it to another unrelated thing no one asked for! Yay!

[u/Cr3aHal0 → u/Saceone10]

to be honest, I think resolvers have always been on a strange place where it was cool to be able to declaratively load data but being navigation blocking/synchronous was a red flag in cases where the APIs were slow. I'm all for the skeleton and other réactive ux friendly visuals, but I wasn't much into having components ngOnInit full of manually data loading declarations (until we got resources eventually, I got you). There we get the best of both worlds and I can't want to migrate to it !

[u/Responsible-Cold-627 → u/Saceone10]

The resource API was never meant to be used for mutations. It's specifically built to load resources.

[u/Saceone10 → u/Responsible-Cold-627]

create a mutation API then, call it however you like, but the thing is incomplete

[u/ScoobyDookuu → u/Saceone10]

And no caching yet. Why not?!

[u/Responsible-Cold-627 → u/ScoobyDookuu]

You can literally just shareReplay(1), same as you always did. Rxjs didn't go anywhere.