• <style>/*...*/</style>

• <div style="..."></div>

• <script>/*...*/</script>

• Style in a separate .css file.
• Script in a separate file.

  <script src="..." ...></script>

  <script id="sap-ui-bootstrap"
    data-sap-ui-onInit="module:..." *
    data-sap-ui-xx-nosync="true"

  ^{* E.g. module:sap/ui/core/ComponentSupport}

Review the reports by UI5 linter and console logs. You might have to increase the log level e.g. via the URL parameter sap-ui-logLevel=ALL to see the relevant logs. Refer to the API reference to learn about newer APIs that replace the deprecated ones.

Note: Some APIs are only partially deprecated. UI5 linter can help detect the use of deprecated options.

sap.m.MessageBox/*...*/;
new myRequiredLib.SomeControl();

<MyControl
  someProperty="{
    path: '...', 
    formatter: 'my.global.format',
    type: 'sap.ui...'
  }"
  someEvent="some.global.handler"
/>

• sap.ui.define when defining a module as part of its dependency list.
• sap.ui.require when simply accessing existing modules without defining a new one.

See Best Practices for Loading Modules on how to access modules in JS.

For XML: Require Modules in XML View and Fragment and Handling Events in XML Views.

Control.extend("my.demo.MyControl", {
  metadata: {/*...*/},
  renderer: MyRequiredRenderer
});

• library.js
• Lib.init's dependencies *
• .library / manifest.json
• ui5.yaml

* If a list of library dependencies is specified in the info object, those libraries will be loaded synchronously if they haven't been loaded yet.

In accordance with the Lib.init description, ensure that all dependencies are declared properly. E.g.:
^{(Without cycle dependencies)}

Only eager dependencies in library.js:

sap.ui.define([
  "sap/ui/core/Lib",
  // ...,
  "sap/m/library", // eager dependency
], (Lib/*, ...*/) => Lib.init({
  // No lazy or transitive dependencies
  dependencies: ["sap.m"/*, "sap.f"*/]
}));

Eager+lazy dependencies in .library, ui5.yaml:

<!-- .library -->
<dependency>
  <libraryName>sap.m</libraryName>
</dependency>
<dependency>
  <libraryName>sap.f</libraryName>
  <lazy>true</lazy>
</dependency>

Bundles such as Component-preload.js or library-preload.js containing JS modules that are in string. For example, due to the bundle having been generated by outdated Grunt build tasks. Or due to using var, let, const, and function outside of sap.ui.define. Result:

"my/ModuleA.js":'sap.ui.define([...'
"my/ModuleB.js":'var myGlobal...'

During the build time, UI5 Tooling logs a warning:

Module [...] requires top level scope and can only be embedded as a string (requires 'eval')

Or an error since specVersion 4 or higher:

Module [...] requires top level scope and can only be embedded as a string (requires 'eval'), which is not supported with specVersion 4.0 and higher.

JS module definitions in the generated preload bundles must not result in string.

If the project still relies on Grunt: migrate to SAP Fiori tools / UI5 Tooling and keep your development toolchain up-to-date. Older SAP Fiori tools versions include utils/locate-reuse-lib.js which should be excluded from the deployment chain.

When defining a module, do not include any global declaration such as var, let, const, and function outside of sap.ui.define.

• Replace e.g. var myGlobal with globalThis.myGlobal, wrap the module definition in an IIFE, or export the global as a separate module that can be required.
• Some third party libraries, such as SheetJS, have to define a variable globally or must be exempted from being modified due to license reasons. In such cases, exclude the third party libraries from the bundle (Sample).
• In UI5 library development, one can also set requiresTopLevelScope="false" to the affected raw-module in .library.