CapabilityUI & Frontend BridgeNode.js, read from its artifacts

Frontend boundary

Exposing a CAP service to a frontend that does not live inside BTP. Authenticating an externally-hosted app against an XSUAA or IAS-protected service, what replaces the approuter when the frontend is on a CDN, destinations from outside BTP, principal propagation, and multitenancy under edge caching.

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

Overview

SAP SHIPS

@sap/appfront-cli

@sap/cds

Scaffolds a starter frontend with cds add vue or cds add react, and wires SAP Build Application Frontend with cds add app-frontend.

SourceVue.js and React UIschecked 2026-08-31

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

THE COMMUNITY ADDS

No community artifact is confirmed here for Node.js.

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

Artifacts2

2 of 2 artifacts

ArtifactSignals

CLI tools1

@sap/appfront-cliCLI for the SAP BTP Application Frontend service

Signals

none

Packages1

@sap/cdsCAP Node.js runtime

Signals

none

Details

Coverage

statecore only, CAP, Node.js, derived

domainUI & Frontend Bridge

For your agent

Ref: capability:frontend-boundary
JSON: /capabilities/frontend-boundary.json
MCP: Connecting an agent