Html-webpack-plugin: Support __webpack_public_path__

[jaroslawr]

When webpack's publicPath option is set, HTMLWebpackPlugin will correctly inject assets with the full path. However, publicPath has a dynamic equivalent that allows specifying the public path at runtime, e.g. when one instance of the app is available under different domains, you can do:

webpack_public_path = document.location.origin + "/";

and webpack itself will use this dynamically set public path for all assets. However, HTMLWebpackPlugin does not support it and will generate plain relative paths when webpack_public_path is used.

[jantimon]

Open for pull requests

[tan31989]

Is this resolved and available? Because we are using the __webpack_public_path__, but the path is not set dynamically.

[jantimon]

Unfortunately this feature request was closed because of inactivity.

[tan31989]

But closing due to inactivity will not give clue about the whether the issue still persists. Would request to make it open and add a label for "help_wanted". At least someone can come forward.

[jantimon]

Agreed but this way its easier to track important issues.. if no one is interested in implementing __webpack_public_path__ it's not really important. would you like to prepare a pull request?

[tan31989]

I might, if I can manage to get some time, but trust me, it's good to add a label saying "help_wanted" rather than closing an issue, which still persists. It's not about no one is interested, it's whether people stumble upon the fact that, this library has this issue which isn't fixed.

IMHO, even when closed, you should specify "No one is helping to fix this" or "Cant fix".

[lock[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.