MobX State Tree React pure reactivity served
summary
MobX State Tree with React shows concrete tradeoffs: runtime type checks catch bad model shapes, the tree produces immutable snapshots and JSON patches so undo/redo and syncing are trivial, and composition plus an environment object for per‑env endpoints keeps stores testable. The demo builds an image gallery wired by provider/inject and observer decorators, with computed values, reactions and actions walked through in code so the model, network fetch, and UI update all actually work.
AI-written summary · about
chapters (5)
- 0:00Start
- 2:28Anything that can be derived from the application state, should be derived. Automatically.
- 9:55MobX State Trees
- 11:24Write imperative code hiding a reactive implementation
- 21:01DEMO TIME
related talks
21mNext-gen React state management with MobX State Tree
43mYou don’t know MobX State Tree
41mmobx-state-tree, stop getting into all those states!
34mImmer-mutable state management
25mNext generation state management
27mReact, But For Data
48mMutable or Immutable? Let's do both!
34mMutable or Immutable? Why not both!