Uncaught RangeError: Maximum call stack size exceeded

Hey all,

I am using webpack-dev-middleware and webpack-hot-middleware and I’m using the setup in my plugins.

                new webpack.HotModuleReplacementPlugin(),

                new ReactRefreshWebpackPlugin({
                    overlay: false
                }),

and the HMR seems to work fine as it is updating the content in the browser but I am getting the following error every time I change a file.

[HMR] Updated modules: process-update.js?e135:127 [HMR] - ./ClientApp/components/shared/Header.jsx process-update.js?e135:132 [HMR] App is up to date. client.js?58a8:241 [HMR] bundle rebuilding client.js?58a8:250 [HMR] bundle rebuilt in 466ms process-update.js?e135:51 [HMR] Checking for updates on the server… bootstrap:1068 Uncaught RangeError: Maximum call stack size exceeded at hotAddUpdateChunk (bootstrap:1068) at webpackHotUpdateCallback (bootstrap:7) at webpackHotUpdateCallback (bootstrap:8) at webpackHotUpdateCallback (bootstrap:8) at webpackHotUpdateCallback (bootstrap:8) at webpackHotUpdateCallback (bootstrap:8) at webpackHotUpdateCallback (bootstrap:8) at webpackHotUpdateCallback (bootstrap:8) at webpackHotUpdateCallback (bootstrap:8) at webpackHotUpdateCallback (bootstrap:8) . . .

I have found a few issues around Github (below) suggesting that I shouldn’t enable --hot option for the WDS together with the HotModuleReplacementPlugin, but I am using WHM.

• https://github.com/webpack/webpack-dev-server/issues/87
• https://github.com/gaearon/react-hot-loader/issues/911

Is there anything I am missing here that I should disable with webpack-dev-middleware for this to not happen?

I have checked that I only have a single webpack module included in the project. `-- webpack@4.44.2

[hasandogu]

@terrencejames I actually attached it to an environment variable and removed the 2nd copy of the HMR if that env variable was set.

PS: I was actually in the middle of an upgrade from .Net Core 3.1 to .Net 5, where the Javascript services and node services don’t work anymore. I took the opportunity to switch to using Razzle instead at the end so that we don’t manage the react refresh plugin directly anymore.

[pmmmwh]

@terrencejames This error will be gone in the next version of the plugin.