Pinia vs Vuex comparison

Introduction

Pinia and Vuex are tools to help manage data in Vue apps. They keep data organized and easy to use across many parts of your app.

When your Vue app grows and you need to share data between many components.

When you want a clear way to update and track changes in your app's data.

When you want to keep your app's state (data) predictable and easy to debug.

When you want to use the latest Vue features with simpler code.

When you want to migrate from Vuex to a more modern and easier state management.

Syntax

Vue

Pinia store example:
import { defineStore } from 'pinia'

export const useCounterStore = defineStore('counter', {
  state: () => ({ count: 0 }),
  actions: {
    increment() {
      this.count++
    }
  }
})

Vuex store example:
import { createStore } from 'vuex'

export const store = createStore({
  state() {
    return { count: 0 }
  },
  mutations: {
    increment(state) {
      state.count++
    }
  }
})

Pinia uses defineStore with a simpler setup and direct state access.

Vuex uses mutations to change state and requires committing mutations.

Examples

Call the action directly on the store instance to update state.

Vue

Pinia action example:
const counter = useCounterStore()
counter.increment()

Use commit to call mutations and update state.

Vue

Vuex mutation example:
store.commit('increment')

Access state directly as properties on the store.

Vue

Pinia state access:
console.log(counter.count)

Access state inside the state object.

Vue

Vuex state access:
console.log(store.state.count)

Sample Program

This Vue app uses Pinia to create a counter store. It increments the count once and shows it in the page.

Vue

/* Pinia example */
import { createApp } from 'vue'
import { createPinia, defineStore } from 'pinia'

const useCounterStore = defineStore('counter', {
  state: () => ({ count: 0 }),
  actions: {
    increment() {
      this.count++
    }
  }
})

const app = createApp({
  setup() {
    const counter = useCounterStore()
    counter.increment()
    return { count: counter.count }
  },
  template: `<div>Count: {{ count }}</div>`
})

app.use(createPinia())
app.mount('#app')

Important Notes

Pinia is the official recommended state manager for Vue 3 and is simpler to learn.

Vuex is more verbose but still works well, especially in older Vue projects.

Pinia supports TypeScript better and has a smaller API surface.

Summary

Pinia is simpler and more modern than Vuex.

Both help manage shared data in Vue apps.

Pinia allows direct state access and simpler actions, Vuex uses mutations and commits.

Practice

1. Which statement best describes the main difference between Pinia and Vuex in Vue applications?

easy

A. Pinia uses direct state access and simpler actions, while Vuex requires mutations and commits.

B. Vuex is simpler and more modern than Pinia.

C. Pinia cannot be used for shared state management.

D. Vuex does not support modular stores.

Solution

1. Step 1: Understand Pinia's approach

   Pinia allows direct access to state and uses simpler actions without the need for mutations.

2. Step 2: Understand Vuex's approach

   Vuex requires state changes to go through mutations and commits, making it more verbose.

3. Final Answer:

   Pinia uses direct state access and simpler actions, while Vuex requires mutations and commits. -> Option A

4. Quick Check:

   Pinia direct access vs Vuex commits [OK]

Hint: Pinia is simpler with direct state, Vuex uses commits [OK]

Common Mistakes:

• Thinking Vuex is simpler than Pinia
• Believing Pinia can't manage shared state
• Assuming Vuex lacks modularity

2. Which of the following is the correct way to define a Pinia store?

easy

A. const useStore = createPinia({ count: 0 })

B. const store = new Vuex.Store({ state: { count: 0 } })

C. const store = createStore({ state: () => ({ count: 0 }) })

D. const useStore = defineStore('main', { state: () => ({ count: 0 }) })

Solution

1. Step 1: Recall Pinia store syntax

   Pinia stores are defined using defineStore with a unique id and a state function.

2. Step 2: Identify correct syntax

   const useStore = defineStore('main', { state: () => ({ count: 0 }) }) matches Pinia's pattern: defineStore('main', { state: () => ({ count: 0 }) }).

3. Final Answer:

   const useStore = defineStore('main', { state: () => ({ count: 0 }) }) -> Option D

4. Quick Check:

   Pinia store uses defineStore [OK]

Hint: Pinia uses defineStore with state as function [OK]

Common Mistakes:

• Confusing Vuex store creation with Pinia
• Using createPinia incorrectly
• Defining state as object instead of function

3. Given this Pinia store code, what will be the output of console.log(store.count) after calling store.increment() once?

const useStore = defineStore('main', {
  state: () => ({ count: 0 }),
  actions: {
    increment() {
      this.count++
    }
  }
})
const store = useStore()
store.increment()

medium

A. 0

B. undefined

C. 1

D. Error: increment is not a function

Solution

1. Step 1: Understand initial state

   The store's count starts at 0 as defined in state.

2. Step 2: Analyze increment action

   The increment method increases count by 1 using this.count++.

3. Step 3: Check the output after calling increment

   After calling store.increment(), count becomes 1.

4. Final Answer:

   1 -> Option C

5. Quick Check:

   Increment increases count to 1 [OK]

Hint: Actions modify state directly in Pinia [OK]

Common Mistakes:

• Expecting count to remain 0
• Confusing actions with mutations
• Assuming increment is undefined

4. Identify the error in this Vuex store mutation and how to fix it:

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

medium

A. Mutations must be called with commit, so use store.commit('increment') instead of store.increment()

B. State should be a function returning an object, not an object directly

C. Mutations cannot modify state directly, use actions instead

D. The mutation name must be uppercase

Solution

1. Step 1: Check how mutations are called in Vuex

   Vuex mutations must be triggered using store.commit('mutationName'), not by calling the mutation function directly.

2. Step 2: Identify the fix

   Replace store.increment() with store.commit('increment') to correctly invoke the mutation.

3. Final Answer:

   Mutations must be called with commit, so use store.commit('increment') instead of store.increment() -> Option A

4. Quick Check:

   Vuex mutations require commit() [OK]

Hint: Use commit() to call Vuex mutations [OK]

Common Mistakes:

• Calling mutation functions directly
• Thinking state must be a function in Vuex root store
• Believing mutations can't modify state

5. You want to migrate a Vuex store to Pinia. Which of these changes is necessary to adapt the Vuex mutation increment(state) { state.count++ } into Pinia's style?

hard

A. Keep the mutation as is and call it with store.commit('increment') in Pinia.

B. Convert the mutation into an action method that directly modifies state using this.count++.

C. Remove the mutation and update state only via getters.

D. Use store.dispatch('increment') to call the mutation in Pinia.

Solution

1. Step 1: Understand Vuex mutation role

   Vuex mutations modify state and are called via commits.

2. Step 2: Understand Pinia's approach

   Pinia does not use mutations; instead, actions directly modify state using this.

3. Step 3: Adapt mutation to Pinia action

   Convert the mutation into an action method that increments this.count directly.

4. Final Answer:

   Convert the mutation into an action method that directly modifies state using this.count++. -> Option B

5. Quick Check:

   Pinia uses actions, no mutations [OK]

Hint: Pinia replaces mutations with direct state changes in actions [OK]

Common Mistakes:

• Trying to use commit() in Pinia
• Using getters to update state
• Calling dispatch() for mutations in Pinia