Vuex? No, it’s X(state)Vue for UI
summary
Argues boolean flags scale poorly and replaces them with concrete state machines using xstate for view and the @xstate/vue hooks, shows a working toggle and image-fetch flow implemented as a machine with context, actions, retries and history, wires a service interpreted and started into component state, runs the demo live so transitions and state updates actually work, and uses the visualizer showing transitions to make testing, debugging and reuse explicit and measurable.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:00Composition Api
- 3:01Set a Local State
- 6:41Bottom-Up Approach
- 10:25Relationship with State Machine and Ui
- 16:02Create a State Machine in View
related talks
31mVuex? No, it’s X(state)Vue for UI
40mVisualize your State Management with XState
48mVueX: Vue.js applications at scale
44mScaling State in Vue: Why XState Matters
31mXState: the Visual Future of State Management- 48mVueX: Vue.js applications at scale
27mXState: the Visual Future of State Management
37mThe Importance of State Management in Vue