This repository was archived by the owner on Apr 8, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 8, 2020. It is now read-only.
Webpack's publicPath isn't used #176
Description
Activity
Thanks for reporting this. The issue was that the
aspnet-webpackmodule overrode theoutputsection of your config when performing in-memory compilation, which meant it didn't pass through yourpathorpublicPathvalues into the compiler.I've just published an updated
aspnet-webpackNPM module - the new version number is 1.0.6. If you update to this version, hopefully you'll find things start working as expected.Indeed, they do. Thanks!
I'm using the html-loader for my angular 2 templates and that replaces for example
<img src>paths with their server path. When I'm running my app in the browser, the publicPath is correctly used as expected. When running on the server, there is no publicPath at all (__webpack_require__.pseems to be the empty string / null / undefined).That means, my browser renders
<img src="/dist/9a08c41631a395a808e4d9d7b7b68d63.jpg"/>, the server just renders<img src="9a08c41631a395a808e4d9d7b7b68d63.jpg"/>.