Knowing how Vuex works is important but knowing when and how to store state in Vuex is equally as important. If you’re working on a large scale Vue app, you may encounter situations where you need the same data at two completely different places in your application. This is the point at which a centralized state management tool like Vuex oftentimes makes a lot of sense.

Today, we will be discussing when to store state in Vuex and then looking at using Vuex modules for separation of concern in large Vuex stores. We’ll be creating a simple customer list app, which allows yours to enter in client information and then view this information in a list. This video already assumes you have a basic understanding of how the Vuex store works with state, mutations, and getters. You can look at my previous video where I go over this topic in or detail.

⚡ RESOURCES ⚡
Vuex - http://next.vuex.vuejs.org/
Source Code - (coming soon)

⭐ TIMESTAMPS ⭐

• 0:00 - Intro
• 1:05 - Reasons for using Vuex
• 1:35 - Alternatives to Vuex
• 2:37 - Using Vuex Flow Chart
• 3:05 - Project
• 3:41 - Vuex Module
• 4:31 - Vuex State/Mutations/Actions
• 5:47 - Vue Components
• 6:51 - Conclusion

#vue #vuex #javascript