Making Vue with Vue
summary
Explains concrete Vuex internals: the store is a single state tree split into modules, Vuex implements reactivity by creating a Vue VM for reactivity with your state, actions are just methods that may return promises, and mutations are wrapped functions that commit by calling them. Describes using Vuex, Vue CLI, Axios and GitLab CI to build Meltano — an ELT data app that loads real warehouse data, updates charts reactively, is open source, and ships after three weeks with a four‑person team.
AI-written summary · about
chapters (18)
- 0:00Introduction to talk
- 1:53DIY vs Vuex for code organization
- 7:07Vuex as centralized state solution
- 10:20Vuex single state tree and modules
- 13:12Vuex reactivity with Vue
- 14:41How Vuex actions work
- 16:04Vuex mutations explained
- 17:32State modification rules in Vuex
- 19:01Melton O app overview
- 22:34Data flow in Melton O
- 24:39Vue CLI benefits for setup
- 25:20DIY vs Vuex with Vue CLI
- 26:02Q&A: Most challenging part
- 28:20Q&A: Open-source project details
- 28:40Q&A: Contributing to project
- 29:42Q&A: Component state management
- 31:05Q&A: What not in Vuex store
- 32:54Q&A: MapState vs MapGetters performance
related talks
49mVue and Vuex: Structure your app with centralized state management
48mVueX: Vue.js applications at scale
26mVuex Modules in practice
37mThe Importance of State Management in Vue
25mHow to stay sane while managing complex state, in Vue js
27mVue and Vuex: The good, the bad and the ugly
47mVue & Vuex
22mThe State of VueX