Angular Signals represent a fundamental shift from stream-based to variable-based reactivity. Unlike RxJS observables, Signals work as reactive variables that automatically track dependencies and trigger updates. The article explores key gotchas including implicit dependency tracking, computed signal caching behavior, and the immediate execution of effects. It provides practical guidance on when to choose Signals over RxJS, recommends flattening state structure instead of deep nesting, and highlights production challenges like input system compatibility and proper effect usage.
Table of contents
Signals as Reactive Variables, Not StreamsGotcha #1: Implicit Dependencies Can BackfireSignals vs. RxJS: Where Signals Shine – and Where They Don’tGotcha #2: Computed Signals Don’t Cache Like You ThinkRethinking State Shape: Signals Love Flat, Not DeepPractical Scenario: Form Label CustomizationGotcha #3: effect() Runs Immediately – And Maybe AgainFinal ThoughtsSort: