New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin is incompatible with [hash] modifier in output.filename [v4-beta] #1346
Comments
Not sure if that is a valid filename - it rather looks like a uri. The html-webpack-plugin gets the filenames which are going to be written to disk - so probably there is no way to get this information about the query string. But feel free to take a look at the code here: Line 601 in dfb98e7
|
I have reported this issue here: webpack/webpack#10638 |
I will try to bring back the same behaviour as in 3.2 for details please see #1355 |
Expected behaviour
The plugin should inject links to compiled .js files with, containing
[hash]
as the query stringCurrent behaviour
Plugin does not inject such files
Environment
Tell us which operating system you are using, as well as which versions of Node.js, npm, webpack, and html-webpack-plugin. Run the following to get it quickly:
Config
...your template file if it is part of this issue: it doesn't matter, I can reproduce even on default template
Additional context
Hi. The plugin does not inject links to compiled js bundles if I specify
[hash]
as query stringwebpackConfig.output.filename
(e.g.[hash].js
- works,bundle.js?[hash]
- does not work)I know that there is HtmlWebpackPlugin() option named
hash: <Boolean>
, and I will use it as temporal workaround, but such way (I mean using [hash] inoutput.filename
) also should work, as i understand (desired behavior was supported on v3)UPD: This issue also affects MiniCssExtractPlugin
Example:
[name]-[hash].css
- works[name].css?[hash]
- doesn't workUPD #2: It seems that it doesn't work if I even add empty query (i.e.
[name].css?
)The text was updated successfully, but these errors were encountered: