Persist and rehydrate your Pinia state between page reloads.
This project use SemVer for versioning. For the versions available, see the tags on this repository.
- π¨ Configurable globally and in every store.
- πͺ Type Safe
- π¦ Extremely small
# npm
npm i pinia-plugin-persistedstate-2
<script src="https://unpkg.com/pinia-plugin-persistedstate-2"></script>
You can find the library on window.PiniaPluginPersistedstate_2
.
All you need to do is add the plugin to pinia:
import { createPinia } from 'pinia'
import { createPersistedStatePlugin } from 'pinia-plugin-persistedstate-2'
const pinia = createPinia()
const installPersistedStatePlugin = createPersistedStatePlugin()
pinia.use((context) => installPersistedStatePlugin(context))
The default storage is localStorage
, but you can also use other storage, e.g., using localForage:
// ...
import localforage from 'localforage'
// ...
pinia.use(
createPersistedStatePlugin({
storage: {
getItem: async (key) => {
return localforage.getItem(key)
},
setItem: async (key, value) => {
return localforage.setItem(key, value)
},
removeItem: async (key) => {
return localforage.removeItem(key)
},
},
}),
)
Serialization and deserialization allow you to customize the state that gets persisted and rehydrated.
For example, if your state has circular references, you may need to use json-stringify-safe to prevent circular references from being thrown:
// ...
import stringify from 'json-stringify-safe'
// ...
pinia.use(
createPersistedStatePlugin({
serialize: (value) => stringify(value),
}),
)
During updates, we may change structure of stores due to refactoring or other reasons.
To support this feature, this plugin provides the migrate
function, which will be called after deserialize
but before actually overwriting/patching the store:
// ...
const store = defineStore(
'store',
() => {
return {
// oldKey: ref(0),
newKey: ref(0),
}
},
{
persistedState: {
overwrite: true,
migrate: (state) => {
if (typeof state.oldKey === 'number') {
return {
newKey: state.oldKey,
}
}
return state
},
},
},
)()
Follow Pinia - Nuxt.js installation steps.
// 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',
],
}
Create the plugin below to plugins config in your nuxt.config.js file.
// nuxt.config.js
export default {
// ... other options
plugins: ['@/plugins/persistedstate.js'],
}
// plugins/persistedstate.js
import { createPersistedStatePlugin } from 'pinia-plugin-persistedstate-2'
export default function ({ $pinia }) {
if (process.client) {
$pinia.use(createPersistedStatePlugin())
}
}
// plugins/persistedstate.js
import { createPersistedStatePlugin } from 'pinia-plugin-persistedstate-2'
import Cookies from 'js-cookie'
import cookie from 'cookie'
export default function ({ $pinia, ssrContext }) {
$pinia.use(
createPersistedStatePlugin({
storage: {
getItem: (key) => {
// See https://nuxtjs.org/guide/plugins/#using-process-flags
if (process.server) {
const parsedCookies = cookie.parse(ssrContext.req.headers.cookie)
return parsedCookies[key]
} else {
return Cookies.get(key)
}
},
// Please see https://github.com/js-cookie/js-cookie#json, on how to handle JSON.
setItem: (key, value) =>
Cookies.set(key, value, { expires: 365, secure: false }),
removeItem: (key) => Cookies.remove(key),
},
}),
)
}
For more details, see type.ts.
-
persist?: boolean
: Defaults totrue
. Whether to persist store. -
storage?: IStorage
: Defaults tolocalStorage
. Where to store persisted state. -
assertStorage?: (storage: IStorage) => void | never
: Perform a Write-Delete operation by default. To ensurestorage
is available. -
overwrite?: boolean
: Defaults tofalse
. Whether to overwrite initial state when rehydrating. When this flat is true usestore.$state = persistedState
,store.$patch(persistedState)
otherwise. -
merge?: (state: S, savedState: S) => S
: Defaults to(state, savedState) => savedState
. A function for merging state when rehydrating state. -
serialize?: (state: S): any
: Defaults toJSON.stringify
. This method will be called right beforestorage.setItem
. -
deserialize?: (value: any): any
: Defaults toJSON.parse
. This method will be called right afterstorage.getItem
. -
filter?: (mutation, state): boolean
: A function that will be called to filter any mutations which will trigger setState on storage eventually.
-
getItem: (key: string) => any | Promise<any>
: Any value other thanundefined
ornull
will be rehydrated. -
setItem: (key: string, value: any) => void | Promise<void>
-
removeItem: (key: string) => void | Promise<void>
Supports all common options. These options are the default values for each store, you can set the most commonly used options in the plugin options, and override/extend it in the store options.
createPersistedStatePlugin({
// plugin options goes here
})
Supports all common options.
defineStore(
'counter-store',
() => {
const currentValue = ref(0)
const increment = () => currentValue.value++
return {
currentValue,
increment,
}
},
{
persistedState: {
// store options goes here
},
},
)
-
key?: string
: Defaults tostore.$id
. The key to store the persisted state under. -
includePaths?: (string | string[])[]
: An array of any paths to partially persist the state. Use dot-notation['key', 'nested.key', ['special.key']]
for nested fields. -
excludePaths?: (string | string[])[]
: Opposite toincludePaths
, An array of any paths to exclude. Due to deep copying,excludePaths
may cause performance issues, if possible, please useincludePaths
instead. -
migrate?: (value: any) => any | Promise<any>
: Themigrate
function enables versioning store. This will be called afterdeserialize
but before actually overwriting/patching the store. -
beforeHydrate?: (oldState: S) => void
: This function gives you the opportunity to perform some tasks before actually overwriting/patching the store, such as cleaning up the old state.
-
store.$persistedState.isReady: () => Promise<void>
: Whether store is hydrated -
store.$persistedState.pending: boolean
: Whether store is persisting
Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.
This project is licensed under the MIT License - see the LICENSE file for details