Stale stats when not using HotModuleReplacementPlugin

💥 Regression Report

Using module.hot is preventing cache clear if not using HotModuleReplacementPlugin or Webpack completely for server. (8f10896058cdfd542c2aca1a982c2e14b1d9707a)

Last working version

Worked up to version: v5.14.2

Stopped working in version: v5.15.0 (commit 8f10896058cdfd542c2aca1a982c2e14b1d9707a)

To Reproduce

Steps to reproduce the behavior:

Download example https://github.com/gregberge/loadable-components/tree/main/examples/server-side-rendering. Run npm run build:webpack -- --watch in one terminal and babel-node src/server/main.js in second.

Then change Test in App.js to Test 2 - you will get old bundles in the HTML and warning Text content did not match. Server: "Test 2" Client: "Test" if you refresh the page.

On v5.14.2 this is working as it should.

Expected behavior

There should be no warning and correct bundles after refresh.

[theKashey]

module.hot is used to understand that module cache can be accessed and operated with. There are better ways to do the same and clearModuleCache is already contain all required checks.

👍 module.hot should be removed

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.