Hopefully, the random file names generated by the package to avoid caching problems

[974758241]

Our packaged file name has always been Component-preload.js and manifest.json, so each deployment has caching problems, if you keep disabling the cache, and will affect the user experience! Can you package the production name is random, so you can avoid caching problems, or we configure NG only index.html no cache on it.

[RandomByte]

If I understand you right, you are requesting a feature to have the output files of a build have unique names in order to implicitly invalidate the browser cache.

I think this is a good idea. But we currently do not plan such a feature for UI5 Tooling.

You could however implement this yourself in a custom build task. Maybe the UI5 community has already done so (check for example https://github.com/ui5-community/ui5-ecosystem-showcase)?

Note that on some platforms you can alternatively make use of the Application Cache Buster: https://sapui5.hana.ondemand.com/#/topic/ff7aceda0bd24039beb9bca8e882825d

[BenReim]

Related: ui5-community/ui5-ecosystem-showcase#168