1.3.1 changed the hash，not sync with html-webpack-plugin about webpack-plugin-hash-output HOT 6 CLOSED

I'll take a look ASAP

from webpack-plugin-hash-output.

I also encounter this issue on version 3.1.1, but version 3.1.0 not has this problem.

from webpack-plugin-hash-output.

@wulucxy, @sunkeysun could you try with

plugins: [
  new WebpackPluginHashOutput(),
  new HtmlWebpackPlugin({
      filename: 'index.html',
      template: 'public/index.html',
      chunks: ['manifest', 'vendor', 'app']
    })
]

(i.e. webpack-plugin-hash-output before html-webpack-plugin)?

According to my test this should fix the problem. If that's the case, I'll update the README and, if possible, try to detect the wrong order and print a warning.

from webpack-plugin-hash-output.

@scinos this is OK。but how is this happen?

from webpack-plugin-hash-output.

TLDR: we changed the webpack phase where the plugin runs and now it competes with html-webpack-plugin

So in v 3.1.1 and 1.3.1 we changed the webpack hook used to run the plugin from after-optimize-chunk-assets to emit. The reason for using after-optimize-chunk-assets in the past was mainly because I didn't know better (😩), I should have used emit form the beginning because it makes more sense. This was also causing bugs with other plugins (#22).

So now it runs in emit. But there are other plugins that also run on emit, like html-webpack-plugin). I do have a test for html-webpack-plugin, and because it run fine, I didn't consider this could break anything, my bad.

For the plugin to work it has to be the first plugin in the emit phase (which is determined by the order of the plugins in your webpack.config.js.

from webpack-plugin-hash-output.

I released a new version (3.2.0) that will print a warning if there are other plugins that might interfere with us:

[WARNING] There are other plugins configured that might interfere with
webpack-plugin-hash-output. For this plugin to work correctly, it should
be the first plugin in the "emit" phase. Please be sure that the rest of the
plugins run after webpack-plugin-hash-output (ensure they are listed after
webpack-plugin-hash-output in the 'plugins' option in your webpack config).

Plugins that could interfere with webpack-plugin-hash-output:
 * HtmlWebpackPlugin

from webpack-plugin-hash-output.