v0.3.0

Remote monitoring in production

Use Remote Redux DevTools to monitor your web, React Native or hybrid apps not only in development, but also in production now!

Start or stop monitoring by using specific actions (for example SOME_ACTION_ERROR).

Check the demo here

It implies that for production you'll host remotedev-server on your side.

The configuration will be like:

export default function configureStore(initialState) {
 return createStore(
    rootReducer,
    initialState,
    devTools({
      name: 'Android app', realtime: false,
      hostname: 'your-host.com', port: 8000,
      startOn: 'SOME_ACTION_ERROR' // or array: ['LOGIN_ERROR', 'LOGOUT_ERROR']
      })
  );
}

For development

If you have process.env.NODE_ENV === 'development', just use devTools() as before and all the changes will be monitored. Otherwise set realtime option to true (devTools({ realtime: true })), but make sure to have it in the development only.

v0.2.2

Relay the whole liftedState when started (#22).

v0.2.1

Support importing state history. Export / import from a file is implemented on [email protected].

v0.2.0

Don't affect the app's performance when not monitored (#20): relay changes only when monitors require it.
It requires using remotedev-app@^0.3.4 and remotedev-server@^0.0.7 (if not using remote server).

v0.1.8

Fixed the issue from last commit, when no options passed (#19)

v0.1.7

• Don't install react anymore, using redux-devtools-instrument. Fix naming collisions like in #11.
• Implement maxAge option. Limit number of maximum allowed actions to be stored on the history tree by default to 30.

v0.1.6

• Warn instead of erroring when connection fails (#18)
• Support store.dispatch request from the monitor app (#17)

v0.1.5

• Fixed filtering monitor actions

v0.1.4

• Add optional filters to reduce noise (#12).
• Just warn when socket is not available instead of showing errors, not to be caught inside the app.

v0.1.2

• Set default hostname if port is set.
• Remove direct redux dependency and encourage to use new redux API.
• Update dependencies to fix some issues in socketcluster and redux-devtools.