Persist and rehydrate a redux store.
Migrations are hot off the presses, feedback welcome!
npm i --save redux-persist
Basic usage requires adding three lines to a traditional redux application:
const store =
For per reducer rehydration logic, you can opt-in by adding a handler to your reducer:
//...case REHYDRATE:var incoming = actionpayloadmyReducerif incoming return ...state ...incoming specialKey:return state
You may also need to configure the persistence layer, or take action after rehydration has completed:
And if things get out of wack, just purge the storage
persistStore(store, [config, callback])
- store redux store The store to be persisted.
- config object
- blacklist array keys (read: reducers) to ignore
- whitelist array keys (read: reducers) to persist, if set all other keys will be ignored.
- storage object a conforming storage engine.
- transforms array transforms to be applied during storage and during rehydration.
- debounce integer debounce interval applied to storage calls.
- callback function will be called after rehydration is finished.
- returns persistor object
- the persistor object is returned by persistStore with the following methods:
- keys array An array of keys to be purged from storage. If not provided all keys will be purged.
- incoming object Data to be rehydrated into the store.
- options object If
serial:true, incoming should be a string, that will be deserialized and passed through the transforms defined in the persistor.
- Manually rehydrates the store with the passed data, dispatching the rehydrate action.
- This is a store enhancer that will automatically shallow merge the persisted state for each key. Additionally it queues any actions that are dispatched before rehydration is complete, and fires them after rehydration is finished.
import constants from 'redux-persist/constants'. This includes rehydration action types, and other relevant constants.
getStoredState / createPersistor
// ...const persistConfig = /* ... */
- under the hood,
persistStoresimply implements both
- getStoredState supports promises as well
const persistor = // persistStore restores and persistsconst secondaryPersistor = // createPersistor only persists
- localStorage (default) web
- localForage (recommended) web, see usage below
- AsyncStorage for react-native
- custom any conforming storage api implementing the following methods:
// react-native// web with recommended localForage
Transforms allow for arbitrary state transforms before saving and during rehydration.
- immutable - support immutable reducers
- compress - compress your serialized state with lz-string
- encrypt - encrypt your serialized state with AES
- custom transforms:
let myTransform =
A common mistake is to fire actions that modify state before rehydration is complete which then will be overwritten by the rehydrate action. You can either defer firing of those actions until rehydration is complete, or you can use an action buffer.
Earlier versions of redux persist included the action buffer by default, but it was removed in v3.
Why Redux Persist
- Performant out of the box (uses a time iterator and operates on state partials)
- Keeps custom rehydration logic in the reducers (where it intuitively belongs)
- Supports localStorage, react-native AsyncStorage, or any conforming storage api
Because persisting state is inherently stateful,
persistStore lives outside of the redux store. Importantly this keeps the store 'pure' and makes testing and extending the persistor much easier.
About Auto Rehydrate
autoRehydrate is a store enhancer that automatically rehydrates state.
While auto rehydration works out of the box, individual reducers can opt in to handling their own rehydration, allowing for more complex operations like data transforms and cache invalidation. Simply define a handler for the rehydrate action in your reducer, and if the state is mutated, auto rehydrate will skip that key.
Auto rehydrate is provided as a convenience. In a large application, or one with atypical reducer composition, auto rehydration may not be convenient. In this case, simply omit autoRehydrate. Rehydration actions will still be fired by
persistStore, and can then be handled individually by reducers or using a custom rehydration handler.