chore: add launchpad dev flow to serve all test apps with one command#809
Open
marianfoo wants to merge 1 commit into
Open
chore: add launchpad dev flow to serve all test apps with one command#809marianfoo wants to merge 1 commit into
marianfoo wants to merge 1 commit into
Conversation
Add `npm run start:launchpad`: boots the CAP server and serves all test
apps behind a Fiori Launchpad in a single process, from source with live
reload via `CDS_PLUGIN_UI5_MODULES={}`. The committed dist config used by
the Docker live demo stays untouched.
- root/examples/server: start:launchpad script chain (mirrors start:server)
- server: add cross-env devDependency for cross-platform env vars
- docs: document the flow in Development/GettingStarted.md
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a one-command dev flow that boots the CAP server and serves all the main test apps behind a Fiori Launchpad in a single process — no separate
fiori runterminals/ports:Auto-opens http://localhost:4004/launchpad.html. Apps are served from source with live reload.
Why
The launchpad infra (
cds-plugin-ui5+cds-launchpad-plugin) already existed, but only as the dist-based Docker live demo. This makes it usable for everyday local development of all apps at once, instead of starting the CAP server and each UI5 app separately.How
start:launchpadscript chain (root → examples → server), mirroring the existingstart:server.CDS_PLUGIN_UI5_MODULES={}, which fully replaces the committedcds-plugin-ui5.modulesconfig so every app falls back to its sourceui5.yaml(live reload) instead ofui5-dist.yaml. The Docker/live-demo dist path is untouched.cross-envdevDependency for cross-platform env-var handling (lockfile change is limited tocross-env).docs/pages/Development/GettingStarted.md.Apps shown:
ordersv2fe,ordersv4fe,ordersv4freestyle,anyupload(those that are server devDependencies and havecrossNavigation.inboundsin their manifest). The wdi5 tests are unaffected — they still launch each app standalone on its own port.Verification
Booted locally against the latest
main: all 4 apps mount from source, the launchpad generates 7 tiles (4 apps + 3 links), and both V4 and V2 (cov2ap) OData services respond.🤖 Generated with Claude Code