How to stay sane while managing complex state, in Vue js
summary
At Framework Summit 2018 a comparison of three concrete patterns shows when each scales: a quick event bus prototype works but becomes untraceable, a simple external object-as-store centralizes state and enforces single-point mutations, and a Vuex store adds explicit actions → mutations → state → getters flow (four observable steps for an async update) plus devtools time-travel debugging. A shopping‑cart demo with persisted items and modularized store code demonstrates modules for domain separation and when to avoid extra Vuex boilerplate.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:30View Components
- 3:19View Custom Events
- 4:04Custom Event Listener
- 5:43What Is an Event Bus
- 14:04Mutations
- 14:54Context Object
- 15:43Getters
- 16:17What Do Components Do with a Very Built in ux Store
- 19:13View X Integrates with the View Depth Tools for Time Travel Debugging
- 19:30View Dev Tools
- 20:54Ux Modules
- 23:53Further Reading
