An HTTPS server or proxy that was previously running on a domain (e.g. localhost), might have set an HSTS header, enforcing Chrome to always use HTTPS for this domain. See https://www.chromium.org/hsts. This makes it impossible to connect to an HTTP-only server running on the same domain.
You need to delete the HSTS mapping in chrome://net-internals/#hsts by entering the domain name (e.g. localhost) and pressing "delete".
Please follow our Contribution Guidelines on how to report an issue.
UI5 CLI stores several kinds of data under your user's home directory in ~/.ui5/:
| Directory | Contents | Safe to delete? |
|---|---|---|
~/.ui5/framework/ |
Downloaded UI5 framework dependencies (one copy per version) | Yes — re-downloaded on next invocation |
~/.ui5/buildCache/ |
Build cache used by ui5 build and ui5 serve (see Build Cache Control) |
Yes — rebuilt on next ui5 build / ui5 serve |
~/.ui5/server/ |
Locally generated SSL certificate and private key for HTTPS / HTTP/2 mode | Yes — regenerated on next HTTPS server start; the new certificate must be re-trusted |
::: warning
Only remove these directories when no UI5 CLI process and no @ui5/* API consumer is actively running. Deleting files that are in use can cause running builds or servers to fail or produce inconsistent results.
:::
Use the dedicated cache clean command, which safely removes all cached data:
ui5 cache cleanThis will display the cache location, the amount of data that will be removed, and ask for confirmation before proceeding. To skip the confirmation prompt (e.g. in CI environments), use the --yes flag:
ui5 cache clean --yesThe command removes the following cached data:
- UI5 Framework packages — downloaded UI5 library files (
~/.ui5/framework/) - Build cache (DB) — build data (
~/.ui5/buildCache/) - Orphaned framework data — incomplete framework directories left over from previously interrupted clean operations (
~/.ui5/.framework_to_delete_*/)
Any missing framework dependencies will be downloaded again during the next UI5 CLI invocation.
::: info
If you have configured a custom data directory via UI5_DATA_DIR or ui5 config set ui5DataDir, replace ~/.ui5/ with that path. See Changing UI5 CLI's Data Directory.
:::
In CI environments or in a combination with other tools, the usage of UI5 CLI's --log-level command parameter might be inconvenient and even impossible.
Replace UI5 CLI's --log-level option with the UI5_LOG_LVL environment variable.
Example:
UI5_LOG_LVL=silly ui5 build
On Windows:
set UI5_LOG_LVL=silly ui5 build
Cross Environment via cross-env:
cross-env UI5_LOG_LVL=silly ui5 build
UI5 + Karma:
cross-env UI5_LOG_LVL=verbose npm run karma
::: warning
The combination of the UI5_LOG_LVL environment variable with the --log-level CLI parameter might lead to unexpected results; they should be used interchangeably but not together. The CLI parameter takes precedence over the UI5_LOG_LVL environment variable.
:::
UI5 CLI's data directory is by default at ~/.ui5. It's the place where the framework artifacts are stored.
In some cases and environments this is not a convenient location and the user needs to provide a better one.
The path to it can either be provided via environment variable or permanently set in the configuration.
::: info Paths are resolved relative to the current root project path (i.e. where the package.json is located).
:::
Unix:
UI5_DATA_DIR=/my/custom/location/.ui5 ui5 buildWindows:
set UI5_DATA_DIR="C:\\my\\custom\\location\\.ui5" ui5 buildConfigure a custom directory:
ui5 config set ui5DataDir /my/custom/location/.ui5Unset the configuration to switch back to the default directory:
ui5 config set ui5DataDir