v2.15.0

• The extension now works on Firefox DevTools panel (not only from a new window as before). @clarkbw #343.
• Support for NaN, Infinity ES6 Symbol, Map and Set data types. @davidfurlong kolodny/jsan#14
• Properly handle replaceReducer when shouldHotReload is set to false. @zalmoxisus #326

v2.14.0

Full support for ES2015 Maps/Sets

To handle these unserializable by JSON.stringify data (and also dates, regexes, undefined, error objects, symbols and functions), set serialize parameter:

const store = Redux.createStore(reducer, window.__REDUX_DEVTOOLS_EXTENSION__ && window.__REDUX_DEVTOOLS_EXTENSION__({
   serialize: true
}));

Keep global Symbols

ES Symbols lose their identity after importing, persisting..., but at least global symbols (Symbol.for) can be safely retained. Thanks to @Velenir for implementing this.

Fixes

• Fix conflicts with Webstorm's extension by not retrieving stored options on page load. Consider specifying options as arguments.
• Fix autoscrolling.

v2.13.2

• Support for Vivaldi browser.
• Deprecate using the Redux Extension inside other extensions in favour of Remote Redux DevTools.

v2.13.1

Revert stringifying Symbols out of the box as not being reliable in case of constructors.

Extended API and helper package to use in production

Restricting available features

Now it's possible to restrict restrict the extension, just specify the features you allow:

const composeEnhancers = composeWithDevTools({
  features: {
    pause: true, // start/pause recording of dispatched actions
    lock: true, // lock/unlock dispatching actions and side effects    
    persist: true, // persist states on page reloading
    export: true, // export history of actions in a file
    import: 'custom', // import history of actions from a file
    jump: true, // jump back and forth (time travelling)
    skip: true, // skip (cancel) actions
    reorder: true, // drag and drop actions in the history list 
    dispatch: true, // dispatch custom actions or action creators
    test: true // generate tests for the selected actions
  },
  // other options like actionSanitizer, stateSanitizer
});

If not specified, all of the features are enabled. When set as an object, only those included as true will be allowed.
Note that except true/false, import and export can be set as custom (which is by default for Redux enhancer), meaning that the importing/exporting occurs on the client side. Otherwise, you'll get/set the data right from the monitor part.

Production optimized package

It's useful to include the extension in production as well. See the blog post for more details.

If you want to restrict it there, use redux-devtools-extension/logOnlyInProduction:

import { createStore } from 'redux';
import { devToolsEnhancer } from 'redux-devtools-extension/logOnlyInProduction';

const store = createStore(reducer, /* preloadedState, */ devToolsEnhancer(
  // options like actionSanitizer, stateSanitizer
));

or with middlewares and enhancers:

 import { createStore, applyMiddleware } from 'redux';
 import { composeWithDevTools } from 'redux-devtools-extension/logOnlyInProduction';

 const composeEnhancers = composeWithDevTools({
   // options like actionSanitizer, stateSanitizer
 });
 const store = createStore(reducer, /* preloadedState, */ composeEnhancers(
   applyMiddleware(...middleware),
   // other store enhancers if any
 ));

You'll have to add 'process.env.NODE_ENV': JSON.stringify('production') in your Webpack config for the production bundle (to envify). If you use react-create-app, it already does it for you.

If you're already checking process.env.NODE_ENV when creating the store, include redux-devtools-extension/logOnly for production enviroment.

Extended API

• autoPause, filter, serialize, latency, stateSanitizer, actionSanitizer

See API reference for more details.

Full support for ImmutableJS out of the box

Now you can persist, import, and investigate ImmutableJS data:

Just pass the Immutable library to the new serialize parameter like so:

import Immutable from 'immutable';
// ...

const store = createStore(rootReducer, window.__REDUX_DEVTOOLS_EXTENSION__ && window.__REDUX_DEVTOOLS_EXTENSION__({
  serialize: {
    immutable: Immutable
  }
}));

It will support all ImmutableJS structures. You can even export them into a file and get them back. The only exception is Record class, for which you should pass in addition the references to your classes:

import Immutable from 'immutable';
// ...

const ABRecord = Immutable.Record({ a:1, b:2 });
const myRecord = new ABRecord({ b:3 }); // used in the reducers

const store = createStore(rootReducer, window.__REDUX_DEVTOOLS_EXTENSION__ && window.__REDUX_DEVTOOLS_EXTENSION__({
  serialize: {
    immutable: Immutable,
    refs: [ABRecord]
  }
}));

New serialize parameter and deprecations

We're deprecating (de)serializeState / (de)serializeAction parameters in favour of the new one:

• serialize (object) - contains { replacer: function, reviver: function, options: object/boolean, refs: array }

  • replacer function(key, value) - JSON replacer function used for both actions and states stringify.

  • reviver function(key, value) - JSON reviver function used for parsing the imported actions and states.

  • options object or boolean:

    • undefined - use regular JSON.stringify to send data - the fast mode.
    • false - handle only circular references.
    • true - handle also dates, regexes, undefined, error objects, symbols, and functions.
    • object, which contains date, regex, undefined, error, and function keys. Fo each of them you can indicate whether to include (if set as true). For function key you can also specify a custom function which handles serialization. See jsan for more details. Example:

    const store = Redux.createStore(reducer, window.__REDUX_DEVTOOLS_EXTENSION__ && window.__REDUX_DEVTOOLS_EXTENSION__({
     serialize: { 
       options: {
        undefined: true,
        function: function(fn) { return fn.toString() }
       }
    }
    }));

  Example of usage with mori data structures:

    const store = Redux.createStore(reducer, window.__REDUX_DEVTOOLS_EXTENSION__ && window.__REDUX_DEVTOOLS_EXTENSION__({
      serialize: {
        replacer: (key, value) => value && mori.isMap(value) ? mori.toJs(value) : value
      }
    }));

File an issue if you still need deSerializeState / deSerializeAction, which were getting the whole root state / action payload, instead of (key, value).

Specify action type key for non-redux apps via getActionType callback parameter

If you're using the extension for non-redux apps, now you can specify what will be shown in the monitors:

window.__REDUX_DEVTOOLS_EXTENSION__.connect({ getActionType: (a) => a.Case })

See elmish/elmish#18 for details.

Big update of Redux DevTools monitors

Time travelling by just jumping to a specific action (#60)

• Visually identify actions from the future.
• Jump to a corresponding state of a specific action.

Source of the demo

Reorder actions (alexkuz/redux-devtools-inspector#64)

Just drag and drop specific actions. It will help to check weird race conditions as stated here and also to better debug features.

Source of the demo

Skip multiple actions at once (gaearon/redux-devtools-log-monitor#47)

Hold shift key while toggling actions:

Persist states right from the extension (#276)

By toggling the Persist button, the states won't be removed from the monitor on unloading the page and will be restored on reload:

Other fixes and improvements:

• Support for ES6 Symbols in action types (alexkuz/redux-devtools-inspector#63).
• Improve styling (alexkuz/redux-devtools-inspector#61).
• Better autoscroll behaviour (alexkuz/redux-devtools-inspector#54).
• More detailed preview and diff for wide layout (alexkuz/redux-devtools-inspector#51).
• Less verbose data in the Chart tooltip (reduxjs/d3-state-visualizer#8).
• Fix disconnect method (#272).
• Support for immutable data export/import (#278).

Fixes and deprecations

Deprecate undocumented getMonitor parameter

In 2.3 we've introduced a method to expose the monitors API (see the release details). The purpose was to let users know when it is dispatched a monitor action or moving back and forth. So one can prevent side effects when time travelling or cancelling actions (see #86, #145, reduxjs/redux-devtools#167).

However, in 2.7 we added a better solution, to lock all the changes (see the post for details). So, we're deprecating getMonitor parameter, which is not necessary anymore. In case you still have a reason to use it, please open an issue.

Fixes

• Fix Import / Export for non-redux apps.
• Don't send the state twice after importing.
• Fix styles in devpanel.

Explore your data with Redux DevTools Extension

Chart and Inspector monitors are combined now. Just click on the node and get detailed tree view. Also now you can see states, actions and diffs as raw data, which can be expanded as a tree as well.

Better serialization and filtering

• Serialiazation is now more performant and takes care of edge cases with circular references. Thanks to @kolodny for working on it!
• Time travelling now is aware of filtered actions and jumps over them.