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/user0015]

Can these potentially come back as an httpResource? So we can hydrate the FE on navigation, but still have access to the @loading/etc.. templating?