Got different hash when run webpack --watch --mode production on different clones of the project?

[nyngwang]

As title. I cloned the same project into another directory on my computer, and I tried to build it in this new location. It turns out the hash is different than the old one. Why? Some of the files of the project are git-ignored, so I have to copy-paste these files into this new location. I guess the hash is different because these files have a different created dates and this info is used when generating the hash?

[alexander-akait]

What is context?

[alexander-akait]

hm, weird, maybe you can provide for which files they are different? Maybe screenshot?

[nyngwang]

where v/ is the folder for vendor files. It's strange that only index.html and the main.[hash].bundle.js changed

[alexander-akait]

Maybe you have loader/plugin which insert - time, hash, path to file, etc, can you look at source code between different versions?

[vankop]

@nyngwang please create a reproducible repo ( try to reduce repo as much as possible ). I will take a look..

[nyngwang]

@vankop Then it will take time. I encountered this problem when working. The project is not sharable. I think this problem is easily reproducible: just create/clone a front-end project using Webpack, where one at ~/SomeFolder, and one at ~/Desktop/Another/Folder.