Yes, in order to benefit from performance optimizations, you have to keep the
/sap.ui5/dependencies/libs always in sync with the UI5 libraries* (incl. custom ones) that can be identified from the application code and visible in API Reference if the lib is from the framework. I.e. not only
"sap.m" but also, for example,
"sap.ui.table" if one of the views contains
If you have libraries which don't need to be preloaded immediately on app start but are supposed to be loaded on-demand, you can assign
"lazy": true to those libraries, e.g.:
"lazy": true is purely informational. In the app, such libs should be loaded explicitly before they're in use:
// Core required from "sap/ui/core/Core"
await Core.loadLibrary("sap.ui.comp", /*async:*/ true);
Further info regarding
* In the context of UI5, a "library" is a named bundle of controls, elements, types, interfaces, etc.
List of such libraries can be found at:
Adding a single module (e.g.
sap/ui/Device) to the
/sap.ui5/dependencies/libs section won't work. To see which library the module belongs to, check the "Library" information from the corresponding API reference page:
The same applies when working with UI5 tooling.
All libraries required by your project must be listed in the
libraries section of the framework configuration:
- name: sap.ui.core
- name: sap.m
- name: sap.ui.table
- name: ...