Deprecating `window.devToolsExtension`

window.devToolsExtension is being deprecated in favour of window.__REDUX_DEVTOOLS_EXTENSION__ and window.__REDUX_DEVTOOLS_EXTENSION_COMPOSE__. See the README on how to use them and the post about why we added the second function.

Also there’s redux-devtools-extension npm package to make things easier.

Now we don’t have the order’s and noop functions’ confusion, also the shared window namespace isn’t too vague anymore. The deprecation warnings will come in the next versions and there will be also more sugar for the npm package.

[zalmoxisus]

@oyeanuj, yes you shouldn’t use both. Best way would be:

let enhancer;
if (window.__REDUX_DEVTOOLS_EXTENSION_COMPOSE__) {
  enhancer = window.__REDUX_DEVTOOLS_EXTENSION_COMPOSE__(
    applyMiddleware(...middleware)
  );
} else {
  enhancer = compose(
    applyMiddleware(...middleware),
    DevTools.instrument(),
    persistState(window.location.href.match(/[?&]debug_session=([^&]+)\b/))
  );
}
store = createStore(
  reducer,
  initialState,
  enhancer
);

New method, window.__REDUX_DEVTOOLS_EXTENSION_COMPOSE__, offers the ability to lock enhancers/middlewares (when the corresponding button is clicked) and to dispatch remote actions through other enhancers. See the blog post for more details. If you don’t need those features, you can just replace window.devToolsExtension with window.__REDUX_DEVTOOLS_EXTENSION__.

Also note that the extension already includes persistState.

[zalmoxisus]

I think 2 years is enough for everybody to rename window.devToolsExtension to window.__REDUX_DEVTOOLS_EXTENSION__ in their apps. We’ll add a deprecation warning in 2.15.5 and remove the variable in 3.0.