Barthélémy Ledoux 4d7f3908df docs: make obvious where the store come from (#1687) 5 years ago
..
README.md 041df8da91 docs: added Scrimba lessons (#1512) 6 years ago
actions.md 2ffedd6b27 docs: Minor typo fix for Actions docs page. (#1606) 5 years ago
forms.md 28284a5e3f fix docs description 5 years ago
getters.md 041df8da91 docs: added Scrimba lessons (#1512) 6 years ago
hot-reload.md ee7c6f3b60 docs: Fix typo in hot-reload.md (#1433) 6 years ago
modules.md 4d7f3908df docs: make obvious where the store come from (#1687) 5 years ago
mutations.md d4d04305e0 docs: update on object spread syntax (#1642) 5 years ago
plugins.md 041df8da91 docs: added Scrimba lessons (#1512) 6 years ago
state.md d4d04305e0 docs: update on object spread syntax (#1642) 5 years ago
strict.md fab5054bc7 docs: reorganize file structure 7 years ago
structure.md fab5054bc7 docs: reorganize file structure 7 years ago
testing.md 041df8da91 docs: added Scrimba lessons (#1512) 6 years ago

README.md

Getting Started

At the center of every Vuex application is the store. A "store" is basically a container that holds your application state. There are two things that make a Vuex store different from a plain global object:

  1. Vuex stores are reactive. When Vue components retrieve state from it, they will reactively and efficiently update if the store's state changes.

  2. You cannot directly mutate the store's state. The only way to change a store's state is by explicitly committing mutations. This ensures every state change leaves a track-able record, and enables tooling that helps us better understand our applications.

The Simplest Store

NOTE: We will be using ES2015 syntax for code examples for the rest of the docs. If you haven't picked it up, you should!

After installing Vuex, let's create a store. It is pretty straightforward - just provide an initial state object, and some mutations:

// Make sure to call Vue.use(Vuex) first if using a module system

const store = new Vuex.Store({
  state: {
    count: 0
  },
  mutations: {
    increment (state) {
      state.count++
    }
  }
})

Now, you can access the state object as store.state, and trigger a state change with the store.commit method:

store.commit('increment')

console.log(store.state.count) // -> 1

Again, the reason we are committing a mutation instead of changing store.state.count directly, is because we want to explicitly track it. This simple convention makes your intention more explicit, so that you can reason about state changes in your app better when reading the code. In addition, this gives us the opportunity to implement tools that can log every mutation, take state snapshots, or even perform time travel debugging.

Using store state in a component simply involves returning the state within a computed property, because the store state is reactive. Triggering changes simply means committing mutations in component methods.

Here's an example of the most basic Vuex counter app.

Next, we will discuss each core concept in much finer details, starting with State.