fix(@angular-devkit/build-angular): ensure to use content hash as filenames hashing mechanism#22612
fix(@angular-devkit/build-angular): ensure to use content hash as filenames hashing mechanism#22612dgp1130 merged 1 commit intoangular:masterfrom alan-agius4:content-hash
Conversation
dgp1130
left a comment
There was a problem hiding this comment.
What exactly was non-deterministic that is fixed? I don't see anything too obvious being changed, is it updating .[hash:${length}] -> .[contenthash:${length}]?
Yes |
|
I think this conflicted with another PR, I'd fix it in GitHub, but I think that will create a merge commit. Probably easier for you to fix when you get a chance @alan-agius4. |
…enames hashing mechanism Previously we used hash which resulted in a unique hash generated for every build even when the contents of the files didn't differ. More info: https://webpack.js.org/guides/caching/#output-filenames
|
Merged to patch in #22623, so retargeting this PR to |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Previously we used hash which resulted in a unique hash generated for every build even when the contents of the files didn't differ.
More info: https://webpack.js.org/guides/caching/#output-filenames
NB: I did try to add a unit test, but it non trivial.