Hot module replacement should trigger render ? about react-transform-hmr HOT 6 CLOSED

Please post a complete project that reproduces the issue. React Transform Boilerplate doesn't have it, therefore it's not the expected behavior. It's hard to guess from a few lines of log. 😉

from react-transform-hmr.

Sorry about that, it's not a react-transform-hmr issue, it was a problem with redux-router and the way I implemented it.

My bad !

from react-transform-hmr.

@gobadiah What was the problem that you had? I'm running into the same thing where HMR says that modules have been updated but it doesn't actually trigger a rerender of the components.

from react-transform-hmr.

I'm having the same issue: Code changes trigger a rebuild and HMR, but the actual UI doesn't get updated. A JavaScript file containing the updated module is successfully loaded into my browser's source tree, but without any effect on the UI. See the following screenshot:

The React Transform Boilerplate works properly for me, so there must be something wrong with my project. I copied all the relevant configuration from the boilerplate to my project.

I'm not using stateless functional components and I don't have any routing in place.

Any ideas?

from react-transform-hmr.

@nhll Give React Hot Loader 3 a try, maybe it will work better for you!

from react-transform-hmr.

Having this problem as well with react 16.2.0 and react-hot-loader 3.1.3. My temporary solution is to pass a random prop into my App component.

  const renderApp = () => {
    ReactDOM.render(
      <Provider store={store}>
        <App random={Math.random()}/>
      </Provider>,
      document.getElementById('app')
    );
  }

  if (module.hot) module.hot.accept('./app', renderApp);

App is a class (class App extends Component) connected to the Redux store (looking for a user), and renders a <Router>.

from react-transform-hmr.