Use NgRx ComponentStore for component-scoped state in Angular
Keep feature-level UI state local with NgRx ComponentStore instead of bloating the global Store with actions only one component cares about.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Keep feature-level UI state local with NgRx ComponentStore instead of bloating the global Store with actions only one component cares about.
Stop iterating through arrays in your NgRx store. Learn how NgRx Entity Adapter normalizes state into ID-keyed maps for O(1) lookups and efficient updates.
NgRx signal stores let you manage component-local UI state without reducer boilerplate. Learn when to use them and when classic NgRx is still better.
Step‑by‑step guide to replace an array‑based feature slice with @ngrx/entity’s normalized shape, including reducer setup, selectors, and verification steps.
Decide whether to put Angular state in the global NgRx Store, a component-scoped ComponentStore, or signalStore based on sharing needs and update frequency.
NgRx Effects isolate async side effects from components. Learn when to use switchMap for reads versus concatMap for writes, and how to keep the action stream alive with proper error handling.
NgRx SignalStore lets you keep component‑level state concise and reactive by exposing source signals and computed signals. This post walks through a concrete todo‑list example, highlights trade‑offs, and gives actionable steps to start using SignalStore in your Angular app.
Tired of writing repetitive CRUD reducers for lists? The NgRx Entity Adapter turns arrays into a normalized dictionary, gives you ready‑made reducer helpers and memoized selectors, and keeps your code type‑safe. Learn how to set it up, trade‑offs, and a real‑world example.
A decision guide that outlines when to use the global NgRx Store versus the scoped ComponentStore, compares trade‑offs, and shows a concrete ComponentStore implementation with validation steps.