4

I have an angular application (angular 6, angular-cli 6.1), when I run a build with the outputHashing flag set to 'all' it always generates files that have the same hash value (chunks, styles, vendor, main and polyfills all get generated with the same hash as they had before, even if they were edited)

This causes a problem when deploying updated versions of the application: the clients will not see the newer version unless they clean their local cache, since the distributed files have the same hash number and won't be downloaded as new files.

On what basis is the hash generated?

And how to force it to create a new value on every build?

Uentee
  • 783
  • 1
  • 7
  • 15
  • have look at this https://stackoverflow.com/questions/49267451/is-angular-clis-output-hashing-always-supposed-to-work-with-lazily-loaded-mod – Abhishek Jan 24 '19 at 16:31
  • I wish to keep the hashing, but have it change on every build, isn't this what the outputHashing is supposed to do? – Uentee Jan 25 '19 at 07:41

0 Answers0