Everything you need to know about Angular Signals
summary
Angular Signals introduces three reactive primitives signal/computed/effect that replace many RxJS patterns, with signals being synchronous stores and computed deriving values automatically. Change detection becomes view-level change detection so updates target exact template fragments. Signals ship in Angular 17+ (18 has developer preview features), core implementation is tiny (2 KB), interops with RxJS via toSignal/fromSignal, and large apps are already using them — YouTube uses signals in production.
AI-written summary · about
chapters (14)
- 0:00Angular Signals intro
- 1:32Why Angular introduced signals
- 3:22Change detection with signals
- 6:13RxJS interoperability
- 6:36Signals API explained
- 10:12Replacing RxJS with computed
- 13:07Effects in signals
- 14:32Writable vs read-only signals
- 15:57RxJS subjects to signals
- 17:27Signals for HTTP requests
- 19:12NgRx signals state
- 20:39Future without Zone.js
- 22:26Signal components
- 23:29Q&A
related talks
51mSignals in Angular: How Do They Work?
24mAngular Architecture using Signals
26mGo Reactive with Angular Signals
20mAngular Signals under the Hood
14mAngular w Signals
35mReactive Angular. At its core.
36mEffective Signals in Angular 19 and above: Rules and Helpers
41mAngular Signals: What's All the Fuss About?