Closed nkbt closed 3 years ago
I assume this will solve the multiple publicPath problem.
Hey all! I've taken over maintenance of the plugin and am doing some housecleaning. For Issues over a year old without a reproduction, we're going to go the route of closing them first. However, they're not dead! If the issue is still pending and still a problem, please reply with a reproduction and we'll reopen post-haste.
Please provide a reproduction by choosing one of the options below:
Provide a minimal repository link (Read https://git.io/fNzHA for instructions). Please use NPM for installing dependencies! These may take more time to triage than the other options.
⚠️ ZIP Files are unsafe and maintainers will NOT download them.
Webpack has added support to use use function as
publicPath
quite a while agoCommit: https://github.com/webpack/webpack/commit/fb4070442a3c0feb115dbb9229ccd0dc1458b30d
At this moment publicPath in
webpack-manifest-plugin
is assumed to be a string, so when I am using function aswebpack.output.publicPath
option, I ended up with something like this in mymanifest.json
:Here is exactly why it is happening: