Angular Signals under the Hood
summary
Deep dive into Angular signals internals with concrete mechanics: signals, computed and effects become nodes in a reactive graph that propagates dirtiness then uses a push-pull phase where consumers pull values in the microtask queue. Version numbers increment only when reference equality changes so computed recalculation skips no-op updates, and dependencies are tracked dynamically (examples with todo arrays, counts, and unchanged-reference updates). Includes code pointers to Angular source and explains how default equals and custom equals affect behavior.
AI-written summary · about
chapters (12)
- 0:00Introduction to signals
- 0:46Core signal API
- 2:14Computed signals and effects
- 3:27Reactivity concept
- 4:50Reactive contexts
- 6:37The reactive graph
- 8:38Push and pull phases
- 10:27Graph optimization
- 11:33Computed signal efficiency
- 13:31Dependency versioning
- 16:54Equality checks
- 18:58Dynamic dependencies & outro
related talks
19mAngular Signals: A Look Under the Hood and Beyond
32mEverything you need to know about Angular Signals
24mAngular Architecture using Signals
41mAngular Signals: What's All the Fuss About?
26mGo Reactive with Angular Signals
31mSignals & fine grained reactivity in Angular
51mSignals in Angular: How Do They Work?
36mEffective Signals in Angular 19 and above: Rules and Helpers