Necromancers Playing MTG
Unleash awesomeness. Private packages, team management tools, and powerful integrations. Get started with npm Orgs »


1.1.0 • Public • Published

Redux PouchDB Plus


Redux PouchDB Plus synchronizes a Redux store with a PouchDB database.

This code is heavily inspired (and some code reused) by Vicente de Alencar's redux-pouchdb. So all Kudos to him. The rewrite was necessary to allow the following extras:

  • Have different Pouch databases for different reducers.
  • Allow to switch databases dynamically.
  • Support for Immutable states beside pure Javascript types.
  • Provide several callbacks (when initialization and database access happens).
  • Allow custom name for PouchDB document used by reducer. (great for multi-user applications)

The code is quite well tested using tape.


General setup

The reducers you wish to persist should be enhanced with this higher order reducer (persistentReducer).

import { persistentReducer } from 'redux-pouchdb-plus';
const counter = (state = {count: 0}, action) => {
  switch(action.type) {
    return { count: state.count + 1 };
    return { count: state.count - 1 };
    return state;
const finalReducer = persistentReducer(counter);

Compose a store enhancer (persistentStore) with other enhancers in order to initialize the persistence.

import { persistentStore } from 'redux-pouchdb-plus';
const db = new PouchDB('dbname');
const applyMiddlewares = applyMiddleware(
const createStoreWithMiddleware = compose(
const store = createStoreWithMiddleware(finalReducer, initialState);

You may also provide a specific database for this reducer (it is prioritized over the provided database to the store).

const db2 = new PouchDB('another_dbname');
const finalReducer = persistentReducer(counter, {db: db2});

A custom name (_id) can also be given to the document created/used for the reducer.

const finalReducer = persistentReducer(counter, {name: 'custom name'});

Switching databases during runtime

You may also provide a function that return a database connector instead of the connector itself. This makes it possible to switch databases dynamically during runtime.

import { reinit } from 'redux-pouchdb-plus';
let dbChoice = 1;
const db = (reducerName, store, additionalOptions) => {
  if (dbChoice === 1)
    return new PouchDB('dbname1');
    return new PouchDB('dbname2');
// uses 'dbname1' database
const finalReducer = persistentReducer(counter, {db});
// switch to 'dbname2' database
dbChoice = 2;
// reinitialize reducer counter
// reinitialize all reducers

Check if database is in sync

With the inSync method you can check if all state changes of persistent reducers are saved to the database or if there is some saving in progress.

import { inSync } from 'redux-pouchdb-plus';
if (inSync()) {
  // do something if the reducer states and the database are in sync

Use Immutable js states

You can use Immutable.js states in your reducers. This works automatically if the initial state is an Immutable.js data type.

// automatically serializes Immutable.js data types to PouchDB
// when the initial state is an Immutable
const counter = (state = Immutable.Map({count: 0}), action) => {
  switch(action.type) {
    return { count: state.count + 1 };
    return { count: state.count - 1 };
    return state;
const finalReducer = persistentReducer(counter);

It is even possible to mix immutable and plain Javascript data as internally transit-immutable-js is used for serialization to the database. Just make sure that the top state container of the reducer is an immutable.

// this is a valid state
Immutable.Map({x: [1, 2, 3]});
// this will open the doors to hell
[1, 2, Immutable.Map({x: 3})];

Provided callback functions

You may provide the following callback functions as addition options to persistentReducer or persistentReducer:

// example for persistentStore, but works the same for persistentReducer function.
persistentStore(counter, {
  onInit: (reducerName, reducerState, store) => {
    // Called when this reducer was initialized
    // (the state was loaded from or saved to the
    // database for the first time or after a reinit action).
  onUpdate: (reducerName, reducerState, store) => {
    // Called when the state of reducer was updated with
    // data from the database.
    // Cave! The store still contains the state before
    // the updated reducer state was applied to it.
  onSave: (reducerName, reducerState, store) => {
    // Called every time the state of this reducer was
    // saved to the database.

Additionally you may provide an onReady callback on the store that is called every time all persistent recuders finished the initialization.

persistentStore(counter, {
  onReady: (store) => {
    // Called when all reducers are initialized (also after
    // a reinit for all reducers is finished).


The current behavior is to have one document for each persisted reducer that looks like:

  _id: 'reducerName', // the name the reducer function, or the name provided by {name: 'custom name'}
  state: {}|[], // the state of the reducer
  _rev: '' // pouchdb keeps track of the revisions


npm i redux-pouchdb-rethink

Downloadsweekly downloads









last publish


  • avatar
Report a vulnerability