Insert the purpose of this project and some interesting info here...
Insert the description here...
Either npm or yarn for dependency management.
Use npm (or yarn) to install the dependencies:
npm install(To use yarn, just do yarn instead.)
Execute the following command to run the app locally for development in watch mode (the browser reloads the app automatically when there are changes in the source code):
npm startAs shown in the terminal after executing this command, the app is then running on http://localhost:8080/index.html. A browser window with this URL should automatically open.
(When using yarn, do yarn start instead. Also for all commands below, you can just replace npm by yarn in this case.)
Execute the following command to build the project and get an app that can be deployed:
npm run buildThe result is placed into the dist folder. To start the generated package, just run
npm run start:distNote that index.html still loads the UI5 framework from the relative URL resources/..., which does not physically exist, but is only provided dynamically by the UI5 tooling. So for an actual deployment you should change this URL to either the CDN or your local deployment of UI5.
For an optimized self-contained build (takes longer because the UI5 resources are built, too), do:
npm run build:optTo start the generated package, again just run:
npm run start:distIn this case, all UI5 framework resources are also available within the dist folder, so the folder can be deployed as-is to any static web server, without changing the bootstrap URL.
With the self-contained build, the bootstrap URL in index.html has already been modified to load the newly created sap-ui-custom.js for bootstrapping, which contains all app resources as well as all needed UI5 JavaScript resources. Most UI5 resources inside the dist folder are for this reason actually not needed to run the app. Only the non-JS-files, like translation texts and CSS files, are used and must also be deployed. (Only when for some reason JS files are missing from the optimized self-contained bundle, they are also loaded separately.)
(When using yarn, do yarn build:opt and yarn start:dist instead.)
To run all tests, do:
npm testThis includes linting and running the unit and integration tests. After the tests have completed, the task ends, so this can be used for automated tests in a continuous integration scenario.
You can manually open test pages by running npm start and then opening one of the following URLs in your browser:
- Unit tests: http://localhost:8080/test/Test.qunit.html?testsuite=test-resources/com/myorg/myapp/testsuite.qunit&test=unit/unitTests
- Integration tests: http://localhost:8080/test/Test.qunit.html?testsuite=test-resources%2Fcom%2Fmyorg%2Fmyapp%2Ftestsuite.qunit&test=integration%2FopaTests
- Both kinds of tests: http://localhost:8080/test-resources/sap/ui/qunit/testrunner.html?testpage=%2Ftest%2Ftestsuite.qunit.html&autostart=true
To lint the code, do:
npm run lintThis project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.