create-easy-ui5 1.0.0

package/.editorconfig

@@ -0,0 +1,21 @@
+# EditorConfig helps developers define and maintain consistent
+# coding styles between different editors and IDEs
+# editorconfig.org
+
+root = true
+
+[*]
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+indent_style = space
+
+[*.md]
+trim_trailing_whitespace = false
+
+[{package.json,ui5.yaml}]
+indent_size = 2
+
+[*.js]
+indent_size = 2

package/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,40 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ""
+labels: ""
+assignees: ""
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+
+- OS: [e.g. iOS]
+- Browser [e.g. chrome, safari]
+- Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+
+- Device: [e.g. iPhone6]
+- OS: [e.g. iOS8.1]
+- Browser [e.g. stock browser, safari]
+- Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

package/.github/ISSUE_TEMPLATE/custom.md

@@ -0,0 +1,7 @@
+---
+name: Custom issue template
+about: Describe this issue template's purpose here.
+title: ""
+labels: ""
+assignees: ""
+---

package/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ""
+labels: ""
+assignees: ""
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

package/.github/workflows/commitlint.yml

@@ -0,0 +1,20 @@
+name: Lint Commit Message
+on:
+  # Trigger the workflow on push or pull request,
+  # but only for the main branch
+  # See: https://github.community/t/duplicate-checks-on-push-and-pull-request-simultaneous-event/18012
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  commitlint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
+      - uses: wagoid/commitlint-github-action@v4

package/.github/workflows/release-auto.yml

@@ -0,0 +1,29 @@
+name: Release (automatic)
+
+on:
+  push:
+    tags:
+      - "v*" # Push events to matching v*, i.e. v1.0, v20.15.10
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    if: "contains(github.event.head_commit.message, 'chore(release): publish')"
+    steps:
+      - uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-node@v2
+        with:
+          node-version: "14"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Publish to NPM
+        run: |
+          echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" > ~/.npmrc
+          echo ":::: Publishing as $(npm whoami)"
+          npm publish
+        env:
+          NPM_TOKEN: ${{ secrets.NPM_RELEASE_AUTH_TOKEN }}

package/.github/workflows/release-manual.yml

@@ -0,0 +1,24 @@
+name: Release (manually)
+
+on:
+  workflow_dispatch:
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: "14"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Publish to NPM
+        run: |
+          echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" > ~/.npmrc
+          echo ":::: Publishing as $(npm whoami)"
+          npm publish
+        env:
+          NPM_TOKEN: ${{ secrets.NPM_RELEASE_AUTH_TOKEN }}

package/.husky/commit-msg

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+npm run hooks:commit-msg

package/.husky/pre-commit

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+npm run hooks:pre-commit

package/.prettierignore

@@ -0,0 +1 @@
+package-lock.json

package/CHANGELOG.md

@@ -0,0 +1,10 @@
+# [1.0.0](https://github.com/ui5-community/create-easy-ui5/compare/f9e81780ee499a24ab573e455cf15e9d190874d4...v1.0.0) (2022-03-10)
+
+### Bug Fixes
+
+- bugfix for arguments and polish docs ([29577d1](https://github.com/ui5-community/create-easy-ui5/commit/29577d14c99453aa869e63da28de1de4d8968862))
+- run easy-ui5 in embedded mode ([f9e8178](https://github.com/ui5-community/create-easy-ui5/commit/f9e81780ee499a24ab573e455cf15e9d190874d4))
+
+### Features
+
+- fully initalize the repo ([532fc33](https://github.com/ui5-community/create-easy-ui5/commit/532fc33ed425730043b682e38b03f631f16d61b6))

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+ui5communityteam@gmail.com.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

package/CONTRIBUTING.md

@@ -0,0 +1,166 @@
+# Contributing to `create-easy-ui5`
+
+## Content
+
+1. [📝 **Reporting Issues**](#-reporting-issues)
+2. [🤩 **Feature Requests**](#-feature-requests)
+3. [🔍 **Analyzing Issues**](#-analyzing-issues)
+4. [💻 **Contributing Code**](#-contributing-code)
+5. [📦 **Releasing Package**](#-releasing-package)
+
+## 📝 Reporting Issues
+
+### Seeking Help / Not a Bug
+
+If you need help setting something up, or if you have questions regarding `create-easy-ui5`, please seek help on a community platform like [StackOverflow](http://stackoverflow.com/questions/tagged/ui5) or the [`#tooling`](https://openui5.slack.com/archives/C0A7QFN6B) channel of the [OpenUI5 Community Slack](https://ui5-slack-invite.cfapps.eu10.hana.ondemand.com/).
+
+### How to Report an Issue
+
+1. **Only `create-easy-ui5` issues**
+2. **No duplicate**: You have searched the [issue tracker](https://github.com/ui5-community/create-easy-ui5/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc) to make sure the bug has not already been reported.
+3. **Good summary**: The summary should be specific to the issue.
+4. **Current bug**: The bug can be reproduced in the most current version of the relevant module(s).
+5. **Reproducible bug**: There are step-by-step instructions provided on how to reproduce the issue.
+6. **Well-documented**:
+   - Precisely state the expected and the actual behavior.
+   - Give information about the environment in which the issue occurs (OS/Platform, Node.js version, etc.).
+   - Generally, give as much additional information as possible.
+7. **Only one bug per report**: Open additional tickets for additional issues.
+8. **Please report bugs in English.**
+
+We encourage you to follow the issue template that will be presented to you when creating a new issue.
+
+When you are ready, report your issue here: https://github.com/ui5-community/create-easy-ui5/issues/new
+
+### Use of Labels
+
+GitHub offers labels to categorize issues. The labels can only be set and modified by committers.
+
+#### General issue categories
+
+- **`bug`**: This issue is a bug in the code.
+- **`documentation`**: This issue is about wrong documentation.
+- **`enhancement`**: This is not a bug report, but an enhancement request.
+
+#### Status of an open issue
+
+- **`information required`**: The author is required to provide information.
+- **`good first issue`**: A newcomer may work on this.
+- **`help wanted`**: Additional help in analyzing this issue is required.
+
+#### Status/resolution of a closed issue
+
+- **`duplicate`**: The issue was already reported somewhere else.
+- **`invalid`**: For any reason, this issue report will not be handled further. Possible reasons are lack of information, or that the issue does not apply anymore.
+- **`wontfix`**: While acknowledged to be an issue, a fix cannot or will not be provided.
+
+### Issue Reporting Disclaimer
+
+We want to improve the quality of the UI5 Communtiy projects and good bug reports are welcome! But keep in mind that this here is spare-time work and thus the capacity is limited.
+
+Therefore, we reserve the right to close or to not process insufficient bug reports in favor of those which are clearly documented and easy to reproduce. Even though we would like to solve each well-documented issue, there is always the chance that it won't happen - please remember: The UI5 Community projects are Open Source and comes without warranty.
+
+Bug report analysis support is always very welcome! See [Analyze Issues](#-analyzing-issues).
+
+## 🤩 Feature Requests
+
+You can request most features by creating an issue in the repository: https://github.com/ui5-community/create-easy-ui5/issues/new
+
+## 🔍 Analyzing Issues
+
+Analyzing issue reports can be a lot of effort. Any help is welcome! 👍
+
+You may be able to add additional or missing information, such as a step-by-step guide on how to reproduce an issue or an analysis of the root cause. In case of the latter, you might even be able to [contribute](#-contributing-code) a bugfix. 🙌
+
+## 💻 Contributing Code
+
+### General Remarks
+
+You are welcome to contribute code to the project in order to fix bugs or to implement new features.
+
+There are three important things to know:
+
+1. You must be aware of the Apache License (which describes contributions).
+2. **Not all proposed contributions can be accepted**. Some features may just fit a third-party add-on better. The code must match the overall direction of the project and improve it. Before contributing a feature, please open a feature request upfront to discuss the necessity of the feature with the core contributors.
+
+### How to Contribute
+
+1. Make sure the change is welcome (see [General Remarks](#general-remarks)).
+2. Create a branch by forking the relevant module repository and apply your change.
+3. Commit and push your change on that branch.
+4. Create a pull request in the relevant repository.
+5. Wait for our code review and approval, possibly enhancing your change on request.
+6. Once the change has been approved and merged, we will inform you in a comment.
+7. Let's celebrate together! 🎉
+
+#### Requirements
+
+The technical requirements to contribute to the project are the following:
+
+- A current version of [Node.js](https://nodejs.org/)
+- A code editor (preferably the free [Microsoft Visual Studio Code](https://code.visualstudio.com/))
+
+#### Getting Started
+
+To get started contributing to this project you need to do the following steps:
+
+- Clone the repository
+- Run `npm install`
+
+#### Commit Messages format
+
+This project enforces the [conventional-commits][conventional_commits] commit message formats.
+The possible commits types prefixes are limited to those defined by [conventional-commit-types][commit_types].
+This promotes a clean project history and enabled automatically generating a changelog.
+
+The commit message format will be inspected both on a git pre-commit hook
+and during the central CI build and will **fail the build** if issues are found.
+
+#### Formatting
+
+[Prettier](https://prettier.io/) is used for some of the sub-packages to do a proper code formatting. The formatting is running as part of the `pre-commit` hook.
+
+#### Compiling
+
+This project is implemented using plain ECMAScript without any compilation / transpilation steps.
+
+#### Testing
+
+There is no testing tooling used for this repository so for. To test the project the simplest way is to run it:
+
+```sh
+# run the project
+npm start
+```
+
+## 📦 Release Package
+
+This repository uses [Lerna](https://github.com/lerna/lerna) to manage the release process.
+
+### Release Process
+
+First, make sure that you pull the latest state of the GitHub repository and then proceed with the following steps:
+
+1. Update the version: `npm version patch|minor|major`
+2. Update the changelog: `npm run changelog`, commit and amend the version change from step 1: `git add . && git commit --amend --no-edit`
+3. Push the new commit and tag: `git push origin --tags`
+4. Inspect the newly artifacts published on npmjs.com.
+
+A GitHub action will do the needful once the new tag has been pushed.
+
+### Upgrading the version of the dependencies
+
+To upgrade the version of the dependencies the NPM package `npm-check-updates` is used. The following code snippets shows how to use it:
+
+```bash
+# install the npm-check-updates
+npm install -g npm-check-updates
+
+# check for dependencies to be updated
+ncu
+
+# update the dependencies automatically
+ncu -u
+```
+
+Be careful with major version changes of the dependencies as this might cause additional work to make the package running again.

package/LICENSE

@@ -0,0 +1,202 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.
+   

package/README.md

@@ -0,0 +1,56 @@
+# npm-init wrapper for Easy-UI5
+
+[![License Status][license-image]][license-url]
+
+This NPM package wraps [Easy-UI5](https://github.com/SAP/generator-easy-ui5) Yeoman generator in [`npm-init`](https://docs.npmjs.com/cli/v8/commands/npm-init), [`npx`](https://docs.npmjs.com/cli/v8/commands/npx) or even just a binary. It automatically benefits from all the available [UI5 Community generators](https://github.com/ui5-community/?q=generator-ui5&type=all&language=&sort=).
+
+## Getting Started
+
+This NPM packages just adds a few more options to use the Easy-UI5 Yeoman generator - but even a bit easier...
+
+### Option 1: Using `npm-init`
+
+The [`npm-init`](https://docs.npmjs.com/cli/v8/commands/npm-init) command is used to setup new repositories. You can use the `create-easy-ui5` package for `npm-init` like this:
+
+```sh
+npm init easy-ui5 [template]
+```
+
+The `create-easy-ui5` package doesn't need to be installed upfront to be used as `npm-init` is downloading it automatically from the central NPM registry.
+
+### Option 2: Using `npx`
+
+The [`npx`](https://docs.npmjs.com/cli/v8/commands/npx) command is used to run NPM packages directly and can be used to run the setup script:
+
+```sh
+npx create-easy-ui5 [template]
+```
+
+The `create-easy-ui5` package doesn't need to be installed upfront to be used as `npm-init` is downloading it automatically from the central NPM registry.
+
+### Option 3: Using `easy-ui5` binary
+
+The `easy-ui5` binary is provided by the `create-easy-ui5` NPM package and once installed it can be used to setup new repositories using the Easy-UI5 Yeoman generator:
+
+```sh
+# Install create-easy-ui5
+npm i -g create-easy-ui5
+
+# Run the binary
+easy-ui5 [template]
+```
+
+## Support
+
+Please use the GitHub bug tracking system to post questions, bug reports or to create pull requests.
+
+## Contributing
+
+We welcome any type of contribution (code contributions, pull requests, issues) to this generator equally.
+
+## License
+
+This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.
+
+[license-image]: https://img.shields.io/github/license/ui5-community/create-easy-ui5.svg
+[license-url]: https://github.com/ui5-community/create-easy-ui5/blob/main/LICENSE

package/index.js

@@ -0,0 +1,34 @@
+#!/usr/bin/env node
+
+// extract the arguments (remove "easy-ui5" if present)
+const args = process.argv.slice(2);
+if (args[0] === "easy-ui5") {
+  args.splice(0, 1);
+}
+
+// create the env for the plugin generator
+const yeoman = require("yeoman-environment");
+const env = yeoman.createEnv(args, {
+  cwd: process.cwd(),
+});
+
+// lookup the easy-ui5 generator
+const generators = env
+  .lookup({
+    localOnly: false,
+  })
+  .filter((sub) => {
+    return sub.namespace === "easy-ui5:app";
+  });
+
+// finally, run the subgenerator
+if (generators[0]?.namespace) {
+  env.run([generators[0].namespace].concat(args), {
+    // verbose: this.options.verbose,
+    embedded: true,
+  });
+} else {
+  console.error(
+    "Easy-UI5 cannot be found! Please run 'npm i -g generator-easy-ui5'!"
+  );
+}

package/package.json

@@ -0,0 +1,57 @@
+{
+  "name": "create-easy-ui5",
+  "version": "1.0.0",
+  "description": "npm-init wrapper for Easy-UI5",
+  "bin": {
+    "easy-ui5": "index.js"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/ui5-community/create-easy-ui5.git"
+  },
+  "keywords": [],
+  "author": "Peter Muessig",
+  "license": "Apache 2.0",
+  "bugs": {
+    "url": "https://github.com/ui5-community/create-easy-ui5/issues"
+  },
+  "homepage": "https://github.com/ui5-community/create-easy-ui5#readme",
+  "engines": {
+    "node": ">=14.0.0"
+  },
+  "scripts": {
+    "start": "node index.js",
+    "format": "prettier --write .",
+    "changelog": "conventional-changelog -p angular -i CHANGELOG.md -s -r 0",
+    "prepare": "husky install",
+    "hooks:pre-commit": "lint-staged",
+    "hooks:commit-msg": "commitlint -e"
+  },
+  "dependencies": {
+    "generator-easy-ui5": "^3.3.0"
+  },
+  "devDependencies": {
+    "@commitlint/cli": "16.2.1",
+    "@commitlint/config-conventional": "16.2.1",
+    "conventional-changelog-cli": "^2.2.2",
+    "cz-conventional-changelog": "3.3.0",
+    "husky": "^7.0.4",
+    "lint-staged": "12.3.4",
+    "prettier": "^2.5.1"
+  },
+  "lint-staged": {
+    "*.{ts,js,json,md,yml}": [
+      "prettier --write ."
+    ]
+  },
+  "config": {
+    "commitizen": {
+      "path": "cz-conventional-changelog"
+    }
+  },
+  "commitlint": {
+    "extends": [
+      "@commitlint/config-conventional"
+    ]
+  }
+}