Safwen

July 30, 2026

Angular's Resource API is finally stable in v22, and I'm genuinely excited about this one. For years Angular apps ran on a hybrid reactivity model: signals for components and business logic, RxJS observables for HTTP through HttpClientModule (or provideHttpClient in standalone apps), and toSignal() gluing the two together. It worked, but you felt the seam every time you crossed it. Resource kills that seam. You get signals all the way down, including HTTP. No more manually tracked isLoading booleans — status is built in with idle, loading, reloading, resolved, error, and local states. abortSignal gives you request cancellation basically identical to a .NET CancellationToken. Streaming resources look like a real replacement for BehaviorSubject-based shared state (notifications, live stats, that kind of thing). And chaining dependent requests with chain() is a much cleaner replacement for the switchMap dance. This is one of those features I've been waiting on since it showed up as a developer preview. Fully signal-reactive apps, no RxJS bridge required, are finally a real option. Full writeup with code examples for every feature: https://safwen.dev/blog/angular-resource-api-is-finally-stable-in-angular-22