Luigi is a micro frontend JavaScript framework that enables you to create an administrative user interface driven by local and distributed views. Luigi allows a web application to communicate with the micro frontends which the application contains. To make sure the communication runs smoothly, you can easily configure the settings such as routing, navigation, authorization, and user experience elements.
Luigi consists of Luigi Core application and Luigi Client libraries. They establish secure communication between the core application and the micro frontend using postMessage API.
Read the Getting started guide to learn more about micro frontends and the structure of Luigi.
Follow the instructions in this document to install Luigi Core. Read this document to install the Luigi Client.
View the application examples to explore Luigi's features.
Go to the Luigi Fiddle site to see Luigi in action and configure a sample application.
For details, see Luigi documentation.
If you want to support Internet Explorer 11 in your application, update your Luigi imports as follows:
<!DOCTYPE html>
<html lang="en">
<head>
<link rel='stylesheet' href='/luigi-core/luigi-ie11.css'>
<!-- <link rel='stylesheet' href='/luigi-core/luigi.css'> -->
</head>
<body>
<script type="module" src="/luigi-core/luigi.js"></script>
<script nomodule src="/luigi-core/luigi-ie11.js"></script>
<!-- <script src="/luigi-core/luigi.js"></script> -->
</body>
</html>import {
linkManager,
uxManager
} from '@kyma-project/luigi-client/luigi-client-ie11';
// } from '@kyma-project/luigi-client';NOTE: The angular example application is not fully compatible with IE11.
For security reasons, follow these guidelines when developing a micro frontend:
- Make the micro frontend accessible only through HTTPS.
- Add Content Security Policies (CSPs).
- Make the Access-Control-Allow-Origin HTTP header as restrictive as possible.
- Maintain a whitelist with trusted domains and compare it with the origin of the Luigi Core application. The origin will be passed when you call the init listener in your micro frontend. Stop further processing if the origin does not match.
NOTE: Luigi follows these sandbox rules for iframes.
All projects in the repository use Prettier to format source code. Run the npm install command in the root folder to install it along with husky, the Git hooks manager. Both tools ensure proper codebase formatting before committing it.
To ensure that existing features still work as expected after your changes, run unit tests using the npm run test command in the core folder.
To ensure that existing features still work as expected after your changes, run UI tests from the Angular example application. Before running the tests, start the sample application by using the npm start command in the application folder.
When the application is ready:
- Run
npm run e2e:openin thecore/examples/luigi-sample-angularfolder to start tests in the interactive mode. - Run
npm run e2e:runin thecore/examples/luigi-sample-angularfolder to start tests in the headless browser.
Use these tests to ensure that applications written for previous versions of Luigi still work after Luigi gets updated with npm. Before running the tests, bundle Luigi by running lerna run bundle in the main repository folder.
Install jq using the brew install jq command. It is required for the script to work, however, you can omit it if the command you are using to run your tests is tagged latest.
- Run
npm run test:compatibilityin the main repository folder to start regression testing. The system will prompt you to select the previous version. - Run
npm run test:compatibility -- --tag latestin the main repository folder to start regression testing with the last version preselected. - On the CI, run
npm run test:compatibility -- --install --tag latestin the main repository folder to install dependencies, bundle Luigi and run the tests with the last version preselected.
Copyright (c) 2019 SAP SE or an SAP affiliate company. All rights reserved. This file is licensed under the Apache-2.0 license except as noted otherwise in the LICENSE file.