Angular Resources: Everything you need to know
summary
Angular Resources replace most RxJS boilerplate with a signal-based API that fetches async data with as little as one line of code using HTTP resource, returning signals like value/hasValue/error/isLoading so templates read data directly with no RxJS boilerplate or async pipe. Resources accept signal-driven params (example: page and pageSize) that automatically trigger new requests, support promises or observables, and already work in production for many, though the APIs remain experimental.
AI-written summary · about
chapters (9)
- 0:00Angular resources intro
- 1:52Why signals matter
- 7:31Signals vs RxJS interop
- 9:38What are resources
- 13:16HTTP resource API
- 15:50Basic HTTP resource example
- 18:22Pagination with signals
- 22:37Why HTTP resource matters
- 24:05Conclusion
related talks
28mExploring Angular's Resource API
24mAngular Architecture using Signals
19mReactive Thinking with Angular Signals and httpResource
36mEffective Signals in Angular 19 and above: Rules and Helpers
58mAngular and The Case for RxJS
46mThe Future of Angular: Faster, Lighter, Stronger
35mReactive Angular. At its core.
32mEverything you need to know about Angular Signals