Ver. 5.6.0: Reference to htmlWebpackPlugin.options.filename in template contains "[name]" instead of actual file name about html-webpack-plugin HOT 7 OPEN

I just published a minimal example at https://github.com/CarlRaymond/html-webpack-plugin-issue1848 with instructions to make it fail and succeed. Thanks!

from html-webpack-plugin.

Yea, thats cool. Just annoying since the version change between this one and the next is only a patch, but broke some of my code that hasn't changed in like a year.

Feels like the 'lazy' part of that is at least a minor change, instead of patch.

No worries though, I'll go through and make some changes on my project to handle this without depending on the .options interface.

from html-webpack-plugin.

Can you put your example using github? thank you

from html-webpack-plugin.

I am having the exact same issue.

My attempt at a workaround was to provide a function to filename to generate the string, but the config just contains a reference to the function, instead of the generated string.

This leads to something along the lines of not processing the output filename before generating the values being passed to the templateContent function.

from html-webpack-plugin.

A little bit of research, and this version was the last version that works.

https://www.npmjs.com/package/html-webpack-plugin/v/5.5.3

from html-webpack-plugin.

Sorry, please never rely on htmlWebpackPlugin.options (it will be removed in the next major release, except title), they are lazy evaleted, otherwise we can't calculate contenthash, so you need to find other logic

from html-webpack-plugin.

A little bit of research, and this version was the last version that works.

https://www.npmjs.com/package/html-webpack-plugin/v/5.5.3

it works because we don't make it lazy, so contenthash doesn't work properly and invalidation was broken

from html-webpack-plugin.