From b3d46df910fb679edb8dd47234db6b4da604eedb Mon Sep 17 00:00:00 2001 From: Scott Addie Date: Tue, 10 Oct 2017 10:35:34 -0500 Subject: [PATCH] Remove HMR section review comment text --- aspnetcore/client-side/spa-services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/client-side/spa-services.md b/aspnetcore/client-side/spa-services.md index 1b7ddea60d..85dc4c8d57 100644 --- a/aspnetcore/client-side/spa-services.md +++ b/aspnetcore/client-side/spa-services.md @@ -162,7 +162,7 @@ The *webpack.config.js* file's `output.publicPath` property tells the middleware ## Hot Module Replacement -Think of Webpack's [Hot Module Replacement](https://webpack.github.io/docs/hot-module-replacement-with-webpack.html) (HMR) feature as an evolution of [Webpack Dev Middleware](#webpack-dev-middleware). HMR introduces all the same benefits, but it further streamlines the development workflow by automatically updating page content after compiling the changes. Don't confuse this with a refresh of the browser, which would interfere with the current in-memory state and debugging session of the SPA. There is a live link between the Webpack Dev Middleware service and the browser, which means changes are ~simply another banned word~ pushed to the browser. +Think of Webpack's [Hot Module Replacement](https://webpack.github.io/docs/hot-module-replacement-with-webpack.html) (HMR) feature as an evolution of [Webpack Dev Middleware](#webpack-dev-middleware). HMR introduces all the same benefits, but it further streamlines the development workflow by automatically updating page content after compiling the changes. Don't confuse this with a refresh of the browser, which would interfere with the current in-memory state and debugging session of the SPA. There is a live link between the Webpack Dev Middleware service and the browser, which means changes are pushed to the browser. ### Prerequisites