You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CSS bundling might not only be helpful in terms of performance, but also in regards to enabling caching mechanisms.
Currently its seems as that there is no straight-forward way of caching and invalidating resources files with a self-contained build. With a self-contained build, the core resource files can not be invalidated using a cachebuster concept as it was formally possible when UI5 Core resources were being loaded from a CDN.
I reported this issue two years ago, but as I am referring specifically to applications, so I think I referred to the theming CSS files when multiple libraries are in use. @RandomByte you might can think about parsing the sap-ui-libraryPreloadCss prameter from index.html and if no app managed preload is used (no leading !), you can merge the theme libraries in the order they appear. If you are interested, look into my gulpfile.js and you should find code, which you likely be able to copy literally 1:1! 🙂 Hope this helps!
Expected Behavior
One CSS file for the whole self-contained build should be loaded, based on the theme selected.
Current Behavior
Multiple CSS files (per library) are loaded separately by the browser, causing some performance degragation.
Steps to reproduce the issue
Context
Affected components
The text was updated successfully, but these errors were encountered: