When we work with SPAs and web applications we need to handle with the browser’s cache. Sometimes we change our static files but the client’s browser uses a cached version of the file instead of the new one. We can tell the user: please empty your cache to use the new version. But most of the times the user doesn’t know what we’re talking about, and we have a problem. There’s a technique called cache buster used to bypass this issue. It consists of a change to the name of the file (or adding an extra parameter), basically to ensure that the browser will send a different request to the server to prevent the browser from reusing the cached version of the file.
When we work with sapui5 application over SCP, we only need to use the cachebuster version of sap-ui-core