Preact-cli: Hashing isn't stable when the file contents haven't changed

[marvinhagemeister]

Do you want to request a _feature_ or report a _bug_?
Bug

What is the current behaviour?

Just noticed that on https://github.com/preactjs/preact-www/pull/338#issuecomment-515845394 that some files have the exact same content, but a different hash with each build. This makes it hard to track size changes across builds.

If the current behaviour is a bug, please provide the steps to reproduce.

1. Run build, check size
2. Run build, check again

What is the expected behaviour?

Filenames stay the same when the content didn't change.

If this is a feature request, what is motivation or use case for changing the behaviour?

See above.

Please mention other relevant information.

Using the latest RC.

[kuldeepkeshwar]

https://github.com/preactjs/preact-cli/blob/4da222985ed6afd1da53767eb0927c30c62920d9/packages/cli/lib/lib/webpack/webpack-client-config.js#L47

will changing chunkhash:5 to chunkhash fix it ?

[ForsakenHarmony]

I don't think so, those 5 characters should also stay the same

[kuldeepkeshwar]

Yup, I tried it. I cloned the project in a different directory & ran the build, got a different hash. it doesn't work.

[ForsakenHarmony]

Might be a webpack problem, but not sure 🤔

[ForsakenHarmony]

any reason we do path based hashing

we do?

[kuldeepkeshwar]

@marvinhagemeister @developit @ForsakenHarmony
I tested above configure with [email protected]. it doesn't output a different hash. Seems like updating webpack fix it.

[prateekbh]

Oooof... That's bad.
Upgrading webpack by a major version is a big deal because of plethora of plugins which might not work

[marvinhagemeister]

Agree, I'd hold off until webpack 5 is at least stable.

[kuldeepkeshwar]

Agree, I'd hold off until webpack 5 is at least stable.

plus the plugin chain 🙂