Pinia vs Vuex comparison - Quick Revision & Key Differences

Recall & Review

beginner

What is Pinia in Vue.js?

Pinia is the official state management library for Vue.js that is simpler and more modern than Vuex. It uses a modular store system and integrates well with Vue 3's Composition API.

intermediate

How does Vuex manage state compared to Pinia?

Vuex uses a centralized store with mutations and actions to manage state changes, which can be more verbose. Pinia simplifies this by allowing direct state modification and uses actions without mutations.

intermediate

What are the benefits of Pinia over Vuex?

Pinia offers simpler syntax, better TypeScript support, modular stores, and easier integration with Vue 3 features. It also supports hot module replacement and devtools out of the box.

beginner

Can Vuex be used with Vue 3?

Yes, Vuex can be used with Vue 3, but it was designed before Vue 3 and the Composition API. Pinia is recommended for Vue 3 projects because it is built to work seamlessly with the new API.

intermediate

How do Pinia and Vuex differ in terms of mutations?

Vuex requires mutations to change state, which are synchronous and must be committed. Pinia does not require mutations; state can be changed directly inside actions, making code simpler.

Which state management library is officially recommended for Vue 3?

A Vuex

B Pinia

C Redux

D MobX

Pinia is the official state management library designed for Vue 3.

In Vuex, how do you change the state?

A Use mutations to commit changes

B Directly modify state in actions

C Use getters to change state

D Use computed properties

Vuex requires mutations to commit state changes.

Which feature does Pinia support that simplifies TypeScript usage?

A No need for type declarations

B Only supports JavaScript

C Requires manual type casting

D Automatic type inference

Pinia supports automatic type inference, making TypeScript easier.

Which library requires more boilerplate code for state management?

A Pinia

B Neither requires boilerplate

C Vuex

D Both are equal

Vuex requires more boilerplate with mutations and actions.

Can Pinia be used with Vue 2?

A Yes, with a plugin

B No, only Vue 3

C Yes, fully supported

D No, it is a React library

Pinia can be used with Vue 2 using a plugin, but it is designed for Vue 3.

Explain the main differences between Pinia and Vuex in managing state in Vue applications.

Think about how each library handles state changes and code complexity.

Describe why Pinia is preferred for Vue 3 projects over Vuex.

Consider Vue 3 features and developer experience.

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