[FEATURE] Bundling: Remove option 'usePredefineCalls' #957
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced May 21, 2024
RandomByte
approved these changes
May 28, 2024
flovogt
added a commit
to SAP/ui5-builder
that referenced
this pull request
May 28, 2024
…on wrappers (#1021) Up until UI5 Tooling v3, the bundle option "usePredefineCalls" defaults to "false" and has to be activated explicitly in a custom bundle configuration. For default bundles, such as Component-preload or self-contained bundle (sap-ui-custom.js), there is no way to use the option apart from re-defining the whole bundle via custom bundle definition. With UI5 Tooling v4 bundles are generated with the usage sap.ui.predefine calls instead of the former default function wrapper. This leads to smaller bundle sizes and less overhead at runtime. As the option only affects the internal handling of bundling without affecting the actual users, the option is removed completely, instead of just changing the default value of the option. Documentation update covered in UI5/cli#957. JIRA: CPOUI5FOUNDATION-760 BREAKING CHANGE: Created bundles use sap.ui.predefine instead function wrappers. For projects this is a compatible change. Only the produced bundle content changes.
18 tasks
d3xter666
pushed a commit
that referenced
this pull request
Sep 24, 2025
…nstead function wrappers (#1021) Up until UI5 Tooling v3, the bundle option "usePredefineCalls" defaults to "false" and has to be activated explicitly in a custom bundle configuration. For default bundles, such as Component-preload or self-contained bundle (sap-ui-custom.js), there is no way to use the option apart from re-defining the whole bundle via custom bundle definition. With UI5 Tooling v4 bundles are generated with the usage sap.ui.predefine calls instead of the former default function wrapper. This leads to smaller bundle sizes and less overhead at runtime. As the option only affects the internal handling of bundling without affecting the actual users, the option is removed completely, instead of just changing the default value of the option. Documentation update covered in #957. JIRA: CPOUI5FOUNDATION-760 BREAKING CHANGE: Created bundles use sap.ui.predefine instead function wrappers. For projects this is a compatible change. Only the produced bundle content changes.
d3xter666
pushed a commit
that referenced
this pull request
Sep 25, 2025
…ad function wrappers (SAP/ui5-builder#1021) Up until UI5 Tooling v3, the bundle option "usePredefineCalls" defaults to "false" and has to be activated explicitly in a custom bundle configuration. For default bundles, such as Component-preload or self-contained bundle (sap-ui-custom.js), there is no way to use the option apart from re-defining the whole bundle via custom bundle definition. With UI5 Tooling v4 bundles are generated with the usage sap.ui.predefine calls instead of the former default function wrapper. This leads to smaller bundle sizes and less overhead at runtime. As the option only affects the internal handling of bundling without affecting the actual users, the option is removed completely, instead of just changing the default value of the option. Documentation update covered in #957. JIRA: CPOUI5FOUNDATION-760 BREAKING CHANGE: Created bundles use sap.ui.predefine instead function wrappers. For projects this is a compatible change. Only the produced bundle content changes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Up until UI5 Tooling v3, the bundle option "usePredefineCalls" defaults to "false" and has to be activated explicitly in a custom bundle configuration.
For default bundles, such as Component-preload or self-contained bundle (sap-ui-custom.js), there is no way to use the option apart from re-defining the whole bundle via custom bundle definition.
With UI5 Tooling v4 bundles are generated with the usage sap.ui.predefine calls instead of the former default function wrapper. This leads to smaller bundle sizes and less overhead at runtime.
As the option only affects the internal handling of bundling without affecting the actual users,
the option is removed completely, instead of just changing the default value of the option.
Implementation covered in SAP/ui5-builder#1021.
JIRA: CPOUI5FOUNDATION-760