The Case For NGXS
summary
Claims that NGXS keeps Angular patterns (decorators, classes, DI) and avoids no reducers or unfamiliar functional constructs with feature states mapped to classes. Actions are class-based, actions as classes with lifecycle and cancelable and handlers can return promises or async/await; dispatch returns an observable so dispatch returns observable allowing sequencing and action completion ties to async work. Selectors are pure, composable and memoized, apps are tree-shakable, many community plugins exist, adoption is ~one quarter to one third of ngrx and conversions often take one to four days.
AI-written summary Β· about
chapters (5)
related talks
37mNGXS - State Management Made Simple
24mNGRX, or NGXS, or Akita, which one should you choose?
28mProgressive State Management: NGXS
20mState Management at Scale w/NgRx
28mYou Might Not Need NgRx
26mState Management Patterns and Best Practices with NgRx
20mComplexity Management with NgRx
35mAdvanced NgRx Techniques