You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having an issue when running Webpack with the --watch option.
If I manually modify the javascript file that gets compiled and inlined, the file does get compiled and built into the dist directory, but the html file isn't updated and the inlined code stays outdated.
If I manually modify the html file, then the inline code does get updated.
Doing some minor debugging of the plugin source code...
HtmlWebpackInlineSourcePlugin.prototype.apply=function(compiler){varself=this;// Hook into the html-webpack-plugin processingcompiler.hooks.compilation.tap('html-webpack-inline-source-plugin',compilation=>{// this line is reached every time a change is made to the source codeself.htmlWebpackPlugin.getHooks(compilation).alterAssetTagGroups.tapAsync('html-webpack-inline-source-plugin',(htmlPluginData,callback)=>{// this line is only reached on the first iteration (when manually running webpack --watch but not when changes are detected)if(!htmlPluginData.plugin.options.inlineSource){returncallback(null,htmlPluginData);}varregexStr=htmlPluginData.plugin.options.inlineSource;varresult=self.processTags(compilation,regexStr,htmlPluginData);callback(null,result);});});};
Maybe there's an issue with the way the plugin is hooking into html-webpack-plugin processing?
Running version 1.0.0-beta.2 of this plugin and 4.2.0 of html-webpack-plugin.
The text was updated successfully, but these errors were encountered:
I'm having an issue when running Webpack with the
--watch
option.If I manually modify the javascript file that gets compiled and inlined, the file does get compiled and built into the
dist
directory, but thehtml
file isn't updated and the inlined code stays outdated.If I manually modify the html file, then the inline code does get updated.
Doing some minor debugging of the plugin source code...
Maybe there's an issue with the way the plugin is hooking into html-webpack-plugin processing?
Running version
1.0.0-beta.2
of this plugin and4.2.0
of html-webpack-plugin.The text was updated successfully, but these errors were encountered: