🐛 Bug report
Current Behavior
Using a fairly standard workflow 9 project setup, when changes are made in the project code, hot module replacement works as expected and updates are applied to the local client without a page refresh. However, based on the webpack-dev-server settings here we expect webpack to watch for changes in local copies of node_modules folder for @/av and @/availity scoped packages. When we make those changes - we do see webpack recompile and hmr updates being sent from the server to the client
however we do not see those changes applied, either in an hmr way or by falling back to a page refresh.
Expected behavior
Changes to packages in node modules that are watched by webpack should trigger hmr updates and those changes should be applied and visible on the client.
Reproducible example
Link to internally hosted projects that can reproduce the issue available on request
Suggested solution(s)
Theres a number of settings related to hot module replacement in webpack, and various reports about how migrating from webpack 4 to 5 may break previously working configurations, but i could not find anything specific about HMR updates not being applied to certain files. Also note various loaders like babel-loader have their own impact on HMR.
Your environment
🐛 Bug report
Current Behavior
Using a fairly standard workflow 9 project setup, when changes are made in the project code, hot module replacement works as expected and updates are applied to the local client without a page refresh. However, based on the webpack-dev-server settings here we expect webpack to watch for changes in local copies of node_modules folder for @/av and @/availity scoped packages. When we make those changes - we do see webpack recompile and hmr updates being sent from the server to the client
however we do not see those changes applied, either in an hmr way or by falling back to a page refresh.
Expected behavior
Changes to packages in node modules that are watched by webpack should trigger hmr updates and those changes should be applied and visible on the client.
Reproducible example
Link to internally hosted projects that can reproduce the issue available on request
Suggested solution(s)
Theres a number of settings related to hot module replacement in webpack, and various reports about how migrating from webpack 4 to 5 may break previously working configurations, but i could not find anything specific about HMR updates not being applied to certain files. Also note various loaders like babel-loader have their own impact on HMR.
Your environment