Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
Showing results for 
Search instead for 
Did you mean: 

Project "Luigi" recently introduced the new Luigi Client support library for UI5. This blog post outlines its most important features and tells you a little more about Luigi.

Luigi and UI5

Luigi is an open-source micro frontend framework that comes with a fully SAP Fiori-compliant design and other useful features out of the box. Luigi's aim is to make it easier to adopt a micro frontend architecture for your web apps and make them scalable, modularizable, customizable, and consistent. Luigi Core allows you to create a complete web application, while Luigi Client lets you configure the views/micro frontends contained within the app.

One of Luigi's main advantages is that it is technology agnostic: it supports apps built on any frontend framework. This includes SAPUI5 and OpenUI5, SAP's powerful web toolkits. Therefore, it has always been possible to use Luigi and UI5 together (you can find an example of an OpenUI5 app built with Luigi here). But now, combining the two is even easier thanks to the newly released Luigi Client support library, which provides helper methods for integrating UI5 apps as Luigi micro frontends.

Luigi Client UI5 Support Library


The purpose of the new library is to make development easier by providing functions you can use in your UI5 application.

The Luigi Client UI5 support library offers the following features:

  • Context - allows you to receive a context object from Luigi

  • Auto routing - provides an easier way to keep your UI5 app and Luigi routing in sync

  • Auto routing for modals - synchronizes the routing between Luigi Core and a modal

  • Preload - a special view that can help you when using Luigi's viewGroups feature

One of the scenarios supported by the library is auto routing. Let's say that you have built an app with UI5 with the URL "" and you included it as a Luigi micro frontend in the navigation:

navigation: {
nodes: [
pathSegment: 'ui5app',
label: 'My UI5 app',
viewUrl: '',

Your UI5 app may contain several pages which the user can navigate to, such as "" or "". Normally, this navigation wouldn't trigger a change in the URL of the main Luigi app because the two apps are independent. But thanks to the auto routing feature of the Luigi Client UI5 support library, you can synchronize the routing so that both URLs are updated at the same time. To use the feature, you would need to edit the routes definition of the manifest file in your UI5 app, and add the following:

"pattern": "",
"name": "about",
"target": "about",
"data": {
"luigiRoute": "/myUI5app/about"
"pattern": "",
"name": "settings",
"target": "settings",
"data": {
"luigiRoute": "/myUI5app/settings"

The result should be that navigating to the page within the UI5 app also updates the Luigi route. There are other configurations of the auto routing feature available, for example one where Luigi's virtualTree is enabled. You can find more information about these in the UI5 Support Library documentation.

As you can see, the Luigi Client UI5 support library can be useful if you are a developer who wants to create apps with UI5 and Luigi. Leveraging the power of both allows you to create apps which are flexible, scalable, and compliant with SAP Fiori standards. For more information about the two frameworks, you can read the documentation for Luigi or UI5. If you have further questions, you can also reach the Luigi team on our Slack channel or GitHub discussions page.