Hot reloading resources outside of React (server rendering)

[mridgway]

The examples that show hot reloading of reducers depend on the redux instance being instantiated within a React component. This works for client-only apps, but when you use server-rendering, you need to bootstrap the application and its state prior to calling React.render. Many of the isomorphic examples I've looked at do not work with hot reloading because the reducers are required from a client bootstrap file instead of the top-level app component. It seems like there would have to be some module.hot magic for hot reloading within server-rendered apps.

[gaearon]

Might be related: #301

[gaearon]

I think we want to understand how to do this before 1.0 is shipped.

[wmertens]

@mridgway cool I never considered server side hot reloading! Do you have a code example?

[mridgway]

@wmertens This isn't server-side hot reloading. The client bootstrapping code has to be moved outside of React when rendering on top of existing markup vs. rendering fully on the client.

[gaearon]

@mridgway

Does something like

import * as reducers from './reducers';

// ...

let store = createStore(combineReducers(reducers));

// ...

React.render(<Stuff />, ...);

if (module.hot) {
  module.hot.accept('./reducers', function () {
    store.replaceReducer(combineReducers(reducers));
  });
}

work?

[gaearon]

Let's continue the discussion in #350.

[gaearon]

Now we encourage people to use hot module replacement API directly, so that you have full control: #667