Fix webpack HMR proxying logic for apps running on non-root URLs (e.g., full IIS virtual directories) #592

New Issue

fergalmoran · 2025-08-09T17:16:53Z

fergalmoran commented

2025-08-09 17:16:53 +00:00

Originally created by @SteveSandersonMS on 7/11/2017

Previously the proxying logic handled nonempty PathBase values incorrectly. Also it didn't allow for Webpack publicPath values being set dynamically at runtime via <base href>. Both of these are needed for HMR to work correctly if the app is hosted in a virtual directory.

This change, along with an update to the aspnet-webpack NPM package, will fix #488

*Originally created by @SteveSandersonMS on 7/11/2017* Previously the proxying logic handled nonempty `PathBase` values incorrectly. Also it didn't allow for Webpack `publicPath` values being set dynamically at runtime via `<base href>`. Both of these are needed for HMR to work correctly if the app is hosted in a virtual directory. This change, along with an update to the `aspnet-webpack` NPM package, will fix #488

fergalmoran closed this issue

2025-08-09 17:16:53 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#592