onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →Reference

cap-ui

An MTA that deploys a CAP service, a HANA HDI container and a Fiori elements app into the HTML5 Application Repository, with two destinations to the same CAP service configured side by side.

One com.sap.application.content module uploads miyasutabooksui.zip to the app-host instance of the SAP HTML5 Application Repository service for SAP BTP; a second creates the instance destinations, among them cap-ui-srv2, an OAuth2UserTokenExchange destination built from the xsuaa service key with HTML5.DynamicDestination: true. Beside it the destination service's own init_data creates cap-ui-srv3, NoAuthentication with HTML5.ForwardAuthToken: true against the same ~{srv-api/srv-url}, and a third variant is left commented out with the note that it needs a ServiceInstanceName, so the two routes to the service stand next to each other in one descriptor. The service module runs on @sap/cds ^6 with db.kind: hana-cloud and hdb, and app/books-ui carries its built dist in the repository. Two GitHub Actions workflows sit beside the project, main.yml, named "Build MTA & Deploy it to BTP", which checks out, sets up Node 18 and installs mbt and the dependencies, and merge-pr.yml, which runs pascalgn/automerge-action on pull requests to main.

GitHub0 ★

Facts

Latestv2.10.3ReleasedLast pushLicenceMIT

Where it sits

Lives in
CAP
Demonstrates
DeploymentCAPDeploymentcapabilityGetting an application onto a runtime and keeping it there: build descriptors, deployment topology, service bindings and lifecycle operations. The target runtime determines how the application is packaged and configured.App hostingCAPApp hostingcapabilityWhere a built frontend lives and what serves it — the static files of a frontend application after the build, reachable behind a login and beside the API it talks to, without a web server of your own.DestinationsCAPDestinationscapabilityReaching a system that is not yours — an S/4HANA tenant, an on-premise service, a third-party API — without the address, the credentials or the tunnel being written into the application. The destination is the indirection, and the reason an endpoint can move without a redeploy.
Flavors
Node.jsfrom its runtime
Runs
Cloud Foundry
Requires
SAP HTML5 Application Repository service for SAP BTPSAP HTML5 Application Repository service for SAP BTPartifactThe built Fiori elements app is uploaded to an app-host instance of it rather than served by the CAP service.SAP Destination serviceSAP Destination serviceartifactBoth routes from the app to the CAP service are destinations: one created as an instance destination from the xsuaa service key, one in the destination service's own init_data.

Who is behind it

Mio YasutakeMio YasutakePersonMaintains this
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer

What it declares

Every artifact

Type
Sample
Origin
Independently maintained
Use as
A reference
Runtime
Node.js
Runs on
Cloud Foundry

As a sample

Form
does not say

Connections5

README

quoted from miyasuta/cap-ui under MIT, read
miyasuta/cap-ui/README.mdOn GitHub

Getting Started

Welcome to your new project.

It contains these folders and files, following our recommended project layout:

File or FolderPurpose
app/content for UI frontends goes here
db/your domain models and data go here
srv/your service models and code go here
package.jsonproject metadata and configuration
readme.mdthis getting started guide

Next Steps

  • Open a new terminal and run cds watch
  • (in VS Code simply choose Terminal > Run Task > cds watch)
  • Start adding content, for example, a db/schema.cds.

Learn More

Learn more at https://cap.cloud.sap/docs/get-started/.

MIT, read

History

Latest

v2.10.3

  1. v2.10.2

  2. v2.10.1

On npm
4downloads per week, npm
Weekly downloads for cap-ui26 complete calendar weeks from 2026-04-20 to 2026-10-18; the latest total is 4.20 Apr – 26 Apr: 927 Apr – 3 May: 34 May – 10 May: 711 May – 17 May: 918 May – 24 May: 425 May – 31 May: 31 Jun – 7 Jun: 138 Jun – 14 Jun: 1715 Jun – 21 Jun: 422 Jun – 28 Jun: 629 Jun – 5 Jul: 66 Jul – 12 Jul: 913 Jul – 19 Jul: 220 Jul – 26 Jul: 427 Jul – 2 Aug: 13 Aug – 9 Aug: 510 Aug – 16 Aug: 417 Aug – 23 Aug: 024 Aug – 30 Aug: 631 Aug – 6 Sept: 47 Sept – 13 Sept: 514 Sept – 20 Sept: 321 Sept – 27 Sept: 728 Sept – 4 Oct: 75 Oct – 11 Oct: 312 Oct – 18 Oct: 4

Details

Sources3
GitHub APIdiscovered here, miyasutachecked
github.com/git+ssh://git@github.com/ElemeFE/element.gittree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesnode
deploymentCloud Foundry
latestv2.10.3
first release
releases and cadence3, ~0d median
discovered viaGitHub API · miyasuta
first seen in the atlas
ecosystem and domaincap, operations-and-runtime
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:miyasuta-cap-ui
JSON
/artifacts/miyasuta-cap-ui.json
MCP
Connecting an agent