CapabilityUI & Frontend BridgeNode.js, read from its artifacts

UI5 dev server

Serving a UI5 application from the CDS server while developing, so the UI and the services it calls answer on one port. A folder of files and a UI5 CLI project whose resources the UI5 tooling assembles per request are two different asks of that server, and which of the two a project has is what decides the answer here.

Showing artifacts, examples and content with confirmed Node.js applicability. View All CAP

Overview

SAP SHIPS

No SAP artifact is confirmed here for Node.js.

A Node.js coverage assessment has not been written. View all flavors

THE COMMUNITY ADDS
cds-plugin-ui5

Runs the UI5 CLI express middlewares inside the CDS server for UI5 freestyle and Fiori elements projects, so their resources are served on the CDS server's own port. It finds them in app/, in the folder cds.env.folders.app names, or as a dependency of the CDS server, and mounts each under a path derived from the metadata/name of its ui5.yaml.

Sourcecds-plugin-ui5 — READMEchecked

A Node.js coverage assessment has not been written. View all flavors

Artifacts1

1 of 1 artifacts
ArtifactSignals
CDS plugins1
cds-plugin-ui5UI5 CLI middlewares running inside the CDS server
Signals
Functional boundary

Tasks1Beta

Covers, under conditionsNot assessed
Reach every UI app of a CAP project from one page while developing1 under conditions

A project with more than one UI app gives a developer one page that links all of them, instead of a URL per app to keep and to type.

Covers finding and opening the apps. Whether each app is then served correctly is the other task on this capability, and what a deployed launchpad shows is not this outcome at all.

Covers, under conditionscds-plugin-ui5Each UI5 module it serves is mounted under its own path, and the app pages it knows about are injected into the welcome page. The README states only the case in which that does not happen, the lazy loading option; that the pages are injected otherwise is the reading of that sentence rather than a second statement.

Conditions: Lazy loading is off: the README states that with the lazy loading option the app pages cannot be retrieved and injected

Remaining work: Leave lazy loading off where the welcome page has to list the apps, or accept that the apps are reached by their mount paths instead.

Open artifact →

Details

Coverage
statecommunity only, CAP, Node.js, derived
also inUI5
Comparison properties2

These are the questions used to compare what the artifacts do. Values come from their documentation and may apply to a particular ecosystem or runtime. Each recorded value in the comparison opens its statement and sources.

Where the app sitsWhat serves the resources
For your agent
Ref
capability:ui5-dev-server
JSON
/capabilities/ui5-dev-server.json
MCP
Connecting an agent