Webpack has two components that are very useful during development: The webpack dev server, and hot module replacement. The webpack dev server compiles needed bundles automatically when requested or sources are changed, so you are always served the latest files when requesting a site. Hot module replacement allows parts of your module to be automatically replaced when they are changed on the server. This is especially useful for single page applications where you don’t want to reboot the entire app when a single part is updated.
What about ASP.NET?
Webpack support only exists in ASP.NET Core, there is no real equivalent package on for the older ASP.NET framework.
Unfortunately, not every project I am involved in uses ASP.NET Core. There is an awful lot of code written on the older and mature ASP.NET framework (also known by its primary namespace System.Web) only available on the full .NET framework. It is non-trivial to port these projects to ASP.NET Core.
Sample ASP.NET Web Forms website with HMR in action:
Note that for HMR to work in Microsoft Edge you need to use an
EventSource polyfill, Microsoft Edge does not support server-sent events.
Sidenote: How we call non-Core ASP.NET projects without potential confusion? “System.Web projects”, “classic ASP.NET”, “legacy ASP.NET”?
How to use
To use the package, install SystemWebpack and WebActivatorEx from NuGet:
Then follow the steps in the readme (Usage) to set it up in your own project.
Also check out the ASP.NET Web Forms sample application.