OrganisationCommunity org

UI5 Community

Capabilities2

Provides 2
Integrated frontend dev serverCAPUI5Integrated frontend dev servercapabilityServing a frontend and its backend services together during development, so they can be reached through one local origin. Serving prebuilt files and integrating a frontend toolchain that assembles resources on demand are different requirements.Local developmentCAPLocal developmentcapabilityRunning the whole stack on a laptop against real bindings — the service, the UI and the routing in front of it — without deploying to see a change.
Demonstrates 2
Integrated frontend dev serverCAPUI5Integrated frontend dev servercapabilityServing a frontend and its backend services together during development, so they can be reached through one local origin. Serving prebuilt files and integrating a frontend toolchain that assembles resources on demand are different requirements.Local developmentCAPLocal developmentcapabilityRunning the whole stack on a laptop against real bindings — the service, the UI and the routing in front of it — without deploying to see a change.

Entries5

Group by
EntrySignals
Maintains2
cds-plugin-ui5v0.17.4
Functional boundary

UI5 CLI middlewares running inside the CDS server

dev-approuterv0.7.2
none

Dev-time wrapper for the SAP Application Router

Maintains: samples, sketches and references3
approuterv0.0.1-security
none

Showcase for dev-approuter in front of two UI5 apps

cds-bookshop
none

CAP bookshop showing UI5 development with cds-plugin-ui5

ui5-bookshop-viewer
none

UI5 app consuming the cds-bookshop server via ui5-middleware-cap

Details

History9
  • dev-approuterprovides[capability:local-development].facets → local_stack_part: App Routercapability:local-development curation on 2026-10-15. The capability now compares its options by the part of the local stack each one starts, and this package's own description states the part. Nothing was entered for the two flags: the registry page carries no README, so whether it resolves a cloud binding itself is not stated anywhere read here.
  • cds-plugin-ui5description.what_it_solves → A CDS server serves the files under `app/`. A UI5 CLI project is not a folder of files ready to serve: its framework resources are resolved and its middlewares configured by `ui5.yaml`, and until something runs that chain the project needs a server of its own. This plugin runs it inside the CDS server, for a project in `app/`, in the folder `cds.env.folders.app` names, or added as a dependency of the CDS server. Each project is mounted under a path derived from the `metadata/name` of its `ui5.yaml`, overridable in the `ui5.yaml` itself, in the CDS server's `package.json` or through `CDS_PLUGIN_UI5_MODULES`. In a project it is one development dependency and an existing `ui5.yaml`, on [@sap/cds](artifact:sap-cds) 6.8.2 or higher.The paragraph claimed live transpiling, which the README does not mention, and said nothing about the two facts a reader needs: where a project has to sit and what it has to be. Rewritten from the README's own sentences. capire's plugin list is where the transpiling claim comes from, and it is quoted on the capability instead of asserted here.
  • cds-plugin-ui5provides → capability:ui5-dev-server, with what_it_does, sources and two facet valuesThe edge was a bare ref, so the page said the plugin answered the capability and nothing about how. The README supplies both facet answers and the mount-path behaviour.
  • cds-plugin-ui5compat.cds_range → >=6.8.2The README states the floor: "The plugin requires [`@sap/cds`](https://www.npmjs.com/package/@sap/cds) `>=6.8.2`."
  • cds-plugin-ui5flavors → nodeThe README's opening sentence says it is a cds-plugin for the node runtime, so the flavor is stated rather than derived from the artifact type.
  • cds-plugin-ui5identity.license, source_available → Apache-2.0, trueRead from the package's own README licence section, as its siblings in the same repository already record.
  • cds-plugin-ui5contributors → actor:petermuessigTwo actor files carried the same GitHub login. peter-m-ssig was keyed on a slugified display name — the umlaut in "Peter Müssig" drops out of the slug, so it looked nothing like the crawled petermuessig and nobody spotted the double. Merged onto the login, which is the identity the crawl matches on.
  • cds-plugin-ui5origin_ring → community-orgui5-community is the UI5 ecosystem's community org, the counterpart of cap-js-community. It was absent from the owner table because that table only knew CAP, so this fell through to independent. Found by probing UI5.
  • First entry seenDiscovered via Added by hand, npm registry, capire · plugins.
Profile1
For your agent