Modules for running a UI5 development server
Part of the UI5 Build and Development Tooling
This is an alpha release!
The UI5 Build and Development Tooling described here is not intended for productive use yet. Breaking changes are to be expected.
The UI5 Build and Development Tooling comes along with a web server component to serve a project.
The development server has already a set of middlewares which supports the developer with the following features:
- Translation files with
.properties
extension are properly encoded with ISO-8859-1 - Changes on files with
.less
extension triggers a theme build and delivers the compiled CSS files - Version Info is created automatically (
/resources/sap-ui-version.json
) - List project files with URL (needed exclusively by the OpenUI5 testsuite):
/discovery/app_pages
,/discovery/all_libs
,/discovery/all_tests
ui5 serve
will automatically use an SSL certificate for HTTPS and HTTP/2 servers.
Upon startup it checks if a certificate exists within the path provided. If there is none, a new certificate is created and used.
Hint: If Chrome unintentionally redirects a HTTP-URL to HTTPS, you need to delete the HSTS mapping in chrome://net-internals/#hsts by entering the domain name (e.g. localhost) and pressing "delete".
You can proxy existing (OData) backend services to get around Access-Control-Allow-Origin (CORS) errors.
To do so, you can add a hash of proxied paths in your ui5.yml
. Example (auth is optional):
# ui5.yml
specVersion: '0.1'
metadata:
name: my-awesome-app
type: application
resources:
proxies:
/api/v1: "http://api.of.external.service/v1"
auth: "myproxyusername:myproxypassword"
Please check our Contribution Guidelines.
Please follow our Contribution Guidelines on how to report an issue.
See CHANGELOG.md.
This project is licensed under the Apache Software License, Version 2.0 except as noted otherwise in the LICENSE file.