Alex Okushko - Software Engineer at Google/Firebase | NGUPEx
summary
Announces @ngrx/component-store as a lightweight (about 350 lines) standalone library for local/component state with explicit APIs: select/updater/effect. Shows a cart example where effects use concatMap to serialize add-product network calls, preventing race conditions, and uses a tapResponse pattern to handle success/error without collapsing streams. Component stores clean up on component destroy, can be provided per-component or root, and are production-ready (used in Firebase Console since August).
AI-written summary · about
chapters (22)
- 0:00Start
- 0:29Rethinking State and Angular Applications
- 4:08Persistent State
- 4:44Client State
- 5:50The Problem We'Re Trying To Solve
- 6:40Angular
- 10:03Card Service File Structure
- 14:15Icon Component Changes
- 19:56Component Store
- 20:44Component Store Is a State Management Library
- 22:22Initialize the Component Store
- 22:37Read the State
- 25:05Updating the State
- 28:33Switch Map
- 29:23Merge Map
- 33:34Where Else Could You Use the Component Store
- 36:35Reactive Local Ui State
- 41:10Global Store
- 42:30Ngrx
- 43:05Structure of the Global Store
- 45:58Summary
- 48:31Official Angular Discord
related talks
39mHow to use NgRx ComponentStore?
25mFilling the Gap in State with NgRx ComponentStore
44mAngular + Redux ... stop, what?
34mReactive State Management For Your Angular App
21mSpeaker Q & A
35mClean React Global State Management Without Dependencies
31mNgRx SignalStore: The Ultimate Tool for Modern State Management
31mUnlocking Reactive State Super Powers with NgRx Signal Store