Vuex Modules in practice
summary
Argues that Vuex modules turn a sprawling single store (one file can hit ~400 lines) into isolated units with their own state, getters, actions and mutations so code stays concise and reusable; demonstrates the cart/products example from the Vue docs, shows mutations and state changes in Vue Devtools, warns that missing namespace causes duplicate action runs, explains cross-module reads via rootState, promotes helpers like mapGetters/mapActions for templates and notes Nuxt auto-namespaces and requires state as function.
AI-written summary · about
chapters (6)
- 0:00Start
- 5:08Start with Vuex...
- 7:18Application grows...
- 9:49Start using vuex modules
- 10:26How the structure will look like...
- 24:59Tiny change...
related talks
37mThe Importance of State Management in Vue
48mVueX: Vue.js applications at scale
35mMaking Vue with Vue
25mHow to stay sane while managing complex state, in Vue js
49mVue and Vuex: Structure your app with centralized state management
21mStructuring A Massive Vuex Store
31mVuex 5 Deep Dive
03mDynamic Store Modules with Vuex