md5-hash有问题，

[renmm]

问题：某一个文件的内容改变了，但是文件hash没有改变的情况？

这样导致我上线到服务器上，相同的文件因为有服务器缓存机制，不会被立马刷新，导致访问失败

[dlin-me]

Same here:

File content changes without changing the hash. And also hash is not the same as hash of the content.

[le0nik]

Same here. This plugin is not reliable.

[xiwc]

same question

[Xaber20110202]

有坑，别踩。用了webpack.optimize.CommonsChunkPlugin的话，模块内容未变，模块id变了，必炸。可能要背一个线上故障！
there has a hole, do not enter in!

[alexindigo]

Looks like duplicated of #7, check out it's thread for the solution.

TL;DR The main issue that module ids not being used for hashing, so when only module ids changed, hash doesn't reflect it. Also it's doing maanual sorting over chunk.modules array, making ids to behave unpredictably when used in concert with OccurrenceOrder plugin.

[Thinking80s]

似乎跟moduleId相关

[whq731]

这里有比较详细的解决方案：
https://sebastianblade.com/using-webpack-to-achieve-long-term-cache/#webpackmd5hash

[oodzchen]

Same problem, the hash of manifest.js always remain as d41d8cd, even the content changed. I've searched many times on the internet, still don't get a solution.

[CntChen]

Same problem: Hash don't change when source code change.

1. This plugin is no need any more in webpack4, use contenthash resolve my problem. issues/19

2. webpack4, in which I test this plugin, change it's chunk module properties, the method this plugin get chunk source code to generate MD5 is not correct any more.

3. chunk.mapModules used inside this plugin is deprecated.

>  DeprecationWarning: Chunk.mapModules: Use Array.from(chunk.modulesIterable, fn) instead

[hhhuangqiong]

https://www.npmjs.com/package/webpack-content-md5-hash
plz try my npm package which can solve this problem.