Nuxt.js
Using Pinia with Nuxt is easier since Nuxt takes care of a lot of things when it comes to server side rendering. For instance, you don't need to care about serialization nor XSS attacks. Pinia supports Nuxt Bridge and Nuxt 3. For bare Nuxt 2 support, see below.
Installation
npx nuxi@latest module add pinia
This will add both @pinia/nuxt
and pinia
to your project. If you notice that pinia
is not installed, please install it manually with your package manager: npm i pinia
.
TIP
If you're using npm, you might encounter an ERESOLVE unable to resolve dependency tree error. In that case, add the following to your package.json
:
"overrides": {
"vue": "latest"
}
We supply a module to handle everything for you, you only need to add it to modules
in your nuxt.config.js
file:
// nuxt.config.js
export default defineNuxtConfig({
// ... other options
modules: [
// ...
'@pinia/nuxt',
],
})
And that's it, use your store as usual!
Awaiting for actions in pages
As with onServerPrefetch()
, you can call a store action within asyncData()
. Given how useAsyncData()
works, make sure to return a value. This will allow Nuxt to skip running the action on the client side and reuse the value from the server.
<script setup>
const store = useStore()
// we could also extract the data, but it's already present in the store
await useAsyncData('user', () => store.fetchUser())
</script>
If your action doesn't resolve a value, you can add any non nullish value:
<script setup>
const store = useStore()
await useAsyncData('user', () => store.fetchUser().then(() => true))
</script>
TIP
If you want to use a store outside of setup()
or an injection aware context (e.g. Navigation guards, other stores, Nuxt Middlewares, etc), remember to pass the pinia
instance to useStore()
, for the reasons alluded to here. Retrieving the pinia
instance might vary.
import { useStore } from '~/stores/myStore'
// this line is usually inside a function that is able to retrieve
// the pinia instance
const store = useStore(pinia)
Fortunately, most of the time you don't need to go through this hassle.
Auto imports
By default @pinia/nuxt
exposes a few auto imports:
usePinia()
, which is similar togetActivePinia()
but works better with Nuxt.defineStore()
to define storesstoreToRefs()
when you need to extract individual refs from a storeacceptHMRUpdate()
for hot module replacement
It also automatically imports all stores defined within your stores
folder. It doesn't lookup for nested stores though. You can customize this behavior by setting the storesDirs
option:
// nuxt.config.ts
export default defineNuxtConfig({
// ... other options
modules: ['@pinia/nuxt'],
pinia: {
storesDirs: ['./stores/**', './custom-folder/stores/**'],
},
})
Note the folders are relative to the root of your project. If you change the srcDir
option, you need to adapt the paths accordingly.
Nuxt 2 without bridge
Pinia supports Nuxt 2 until @pinia/nuxt
v0.2.1. Make sure to also install @nuxtjs/composition-api
alongside pinia
:
yarn add pinia @pinia/nuxt@0.2.1 @nuxtjs/composition-api
# or with npm
npm install pinia @pinia/nuxt@0.2.1 @nuxtjs/composition-api
We supply a module to handle everything for you, you only need to add it to buildModules
in your nuxt.config.js
file:
// nuxt.config.js
export default {
// ... other options
buildModules: [
// Nuxt 2 only:
// https://composition-api.nuxtjs.org/getting-started/setup#quick-start
'@nuxtjs/composition-api/module',
'@pinia/nuxt',
],
}
TypeScript
If you are using Nuxt 2 (@pinia/nuxt
< 0.3.0) with TypeScript or have a jsconfig.json
, you should also add the types for context.pinia
:
{
"types": [
// ...
"@pinia/nuxt"
]
}
This will also ensure you have autocompletion 😉 .
Using Pinia alongside Vuex
It is recommended to avoid using both Pinia and Vuex but if you need to use both, you need to tell pinia to not disable it:
// nuxt.config.js
export default {
buildModules: [
'@nuxtjs/composition-api/module',
['@pinia/nuxt', { disableVuex: false }],
],
// ... other options
}