Pinia Disasterclass
summary
Highlights concrete migration pitfalls and fixes for Pinia: common broken patterns from Vuex—do not externalize state, avoid meaningless getters/actions, and prefer business-named actions; don’t cast to any—use generics on ref/reactive to get real type safety; call stores only in places with an active injection context (script setup, navigation guards) to avoid cross-request leaks and SSR failures; prefer router/URL as source of truth for selected resources; previews an experimental data-fetching layer Pinia Colada and notes some SPA-only behaviors.
AI-written summary · about
chapters (7)
- 0:00Introduction and evolution
- 2:40Common state management habits
- 6:12State patterns and safety
- 11:06Avoiding 'yellow' casting
- 13:52Composable patterns and usage
- 21:00Advanced data fetching
- 27:03Conclusion
related talks
42mPinia Disasterclass
48mVUE3 & Pinia A Better Pattern for Global State Management
25mEverything Beyond State Management in Stores with Pinia
35mPinia Colada: Smooth Data Fetching for Better UX
50mClean Async State Management
33mPanel Discussion – State Management
16mEffortless State Management in Nuxt 3 with Pinia: Practical Guide
25mState Management with Composition API