What are UI5 Web Components?
- A rich set of enterprise-grade reusable UI elements driven by a lightweight framework (~20K gzipped).
- Suitable for building anything from static web sites to complex web applications.
- Usable with any current or future web development framework (React, Angular, Vue, etc...).
- Implement the SAP Fiori design and follow the SAP Fiori Design Guidelines for a consistent UX.
- Created and maintained by SAP as part of the UI5 product family.
- Future-proof: being web standards, they are compatible with any version of any web development framework.
- Encapsulated: the HTML/CSS in the shadow DOM are protected from interference by the web page and vice versa, making them stable in any environment and suitable not only for apps, but also for libraries and micro-frontends.
- Elegant: being custom HTML elements, they hide implementation complexity behind a single HTML tag, making them easily usable with the standard DOM APIs.
- UI5 Web Components Home Page
- List of all components and other public APIs
- Configuring UI5 Web Components
- Creating a custom theme
- Creating custom UI5 Web Components
- Creating custom UI5 Web Components NPM packages
- Micro-frontends and Custom elements scoping
- F.A.Q.
OpenUI5 is an open source JS framework that lets you build enterprise-ready web applications, responsive to all devices, running on almost any browser of your choice. It's based on JavaScript, using jQuery as its foundation and follows web standards. It eases your development with a client-side HTML5 rendering library including a rich set of controls and supports data binding to different data models (JSON, XML and OData).
UI5 Web Components…
- …are not built on top of UI5, but rather lightweight and independent UI elements
- …are not a successor of UI5, but rather a complementary offering
- …bring the relevant UI5 qualities and SAP Fiori UX to the HTML level, usable with any web framework
UI5 Web Components are good for…
- …web applications which already use a different web framework
- …static web sites built without web frameworks, to just add a few interactive UI elements
UI5 remains what it is: the best choice for…
- …building complete enterprise-ready and responsive web applications
UI5 Web Components for React is a wrapper implementation around
UI5 Web Components which makes using them in React even more comfortable. The current version of React (react 16) has some
shortcomings when it comes to handling Custom Elements, namely the binding of boolean attributes as well as adding event listeners to custom event names like selection-change. With the help of UI5 Web Components for React, you can use the UI5 Web Components in React as if they were native React components. In addition to that, this library is also offering TypeScript definitions for all components, some complex layout components built on top of UI5 Web Components as well as Charting Components.
-
Install the NPM module(s) that ship the desired UI5 Web Component(s), for example if you need
ui5-button:npm install @ui5/webcomponents
-
Import the desired UI5 Web Component(s) to your app:
import "@ui5/webcomponents/dist/Button.js"; // loads and defines ui5-button
-
Use the UI5 Web Component(s) as you would use any HTML element:
<ui5-button>Hello world!</ui5-button>
For more on using UI5 Web Components, click here.
Note: For a full list of the UI5 Web Components (and the respective NPM modules that ship them), see Public module imports.
No, you are expected to import only the components (or other public APIs) that you are going to use and bundle them along with the rest of your application.
UI5 Web Components are supported by all major modern browsers and can also run on IE11 with a polyfill.
| Browser | Support |
|---|---|
| Chrome | Native |
| Firefox | Native |
| Safari | Native |
| Edge | Native |
| IE 11 | With Polyfill |
If your app needs to support IE11 or legacy Edge, please follow the instructions.
This section might be of interest to you mainly if you need to run or build the project locally
Note: The UI5 Web Components project is set up with the Yarn node package manager. This is because it offers functionality that the otherwise preferred npm package manager is currently lacking. Namely, the workspace setting which is currently used in the UI5 Web Components (mono-)repository. Note that npm might add this feature in the future.
UI5 Web Components contains several projects (NPM packages):
| Project | NPM Package | Description |
|---|---|---|
main |
UI5 Web Components | Bread-and-butter components (buttons, inputs, popups, pickers, tables, etc...) that are generally found in web apps. |
fiori |
UI5 Web Components Fiori | More semantic components, specific to the Fiori UX (shell bar, side navigation, etc...) that are commonly found in SAP apps. |
icons |
UI5 Web Components Icons | A rich icons collection (SAP-icons), suitable for enterprise-grade apps |
base |
UI5 Web Components Base | The UI5 Web Components framework itself |
theme-base |
UI5 Web Components Theme Base | Theming assets (the default theme and additional accessibility themes) |
localization |
UI5 Web Components Localization | i18n functionality and CLDR assets |
playground |
N/A | The playground application |
yarn # to install all dependencies
yarn start # to serve the projectYou can then explore component test pages on:
- http://localhost:8080/test-resources/pages/ for the
mainpackage - http://localhost:8081/test-resources/pages/ for the
fioripackage.
You can start the Playground app with the following commands:
# install palyground specific dependencies (one time only)
cd packages/playground
yarn install:dependencies
# start the playground from the project root
cd ../..
yarn start:playground
# open http://localhost:4000/Note: If you wish to manually install dependencies & run the Playground you can check out our in depth tutorial
To build the UI5 Web Components project, run the following commands:
yarn # to install all dependecies
yarn build # to build the projectAfterwards, you can find the build output in the dist folder of the corresponding package folder.
For example, to find the Button component (that belongs to the main package), look inside the packages/main/dist folder.
Note: Before building the project you can also set the DEPLOY_PUBLIC_PATH environment variable to specify the path where non-bundled assets will be fetched from, for example:
DEPLOY_PUBLIC_PATH=/my/resources/ yarn build
(for Windows: DEPLOY_PUBLIC_PATH="\/my\/resources\/" yarn build)
None as of 1.0.0-rc.8
No major bugs known. To report an issue or view the currently open issues, click here.
We welcome all comments, suggestions, questions, and bug reports. Please follow our Support Guidelines on how to report an issue, or chat with us in the #webcomponents channel of the OpenUI5 Community Slack.
Please check our Contribution Guidelines.