Go Reactive with Angular Signals
summary
Signals arrive in Angular v16 developer preview and claim finer-grained reactivity and improved change detection by treating state as a writable box with get/set/update/mutate, computed values that are memoized and lazy (recompute only when read), and effects for side effects. Interop uses toSignal and toObservable, but toSignal yields a read-only signal so a demo of a users→tasks UI must fall back to creating a writable signal plus an effect and manual subscribe/unsubscribe to make updates work.
AI-written summary · about
chapters (13)
- 0:00Angular Signals intro
- 1:52Why reactivity matters
- 2:56Creating signals
- 5:25Reading and modifying signals
- 7:34Signals as dependencies
- 9:41Signals vs Observables
- 12:29Computed signals power
- 14:17Using effects
- 15:19Signals in templates
- 18:53Reactive data fetching
- 21:19Limitations of toSignal
- 23:26Best practices for signals
- 24:32Signals vs Observables
related talks
32mEverything you need to know about Angular Signals
14mAngular w Signals
31mSignals & fine grained reactivity in Angular
51mSignals in Angular: How Do They Work?
35mReactive Angular. At its core.
20mAngular Signals under the Hood
24mAngular Architecture using Signals
36mEffective Signals in Angular 19 and above: Rules and Helpers