BrowseSAP Cloud Application Programming Model
Everything in CAP
7 of 1054
Type: CDS plugin
Domain: Developer Experience
Origin
Signals
More
Group by: Capability
As a CDS plugin
Distributed through
EntryBySignalsLast activity
DebuggingSAP and community
@cap-js/console@cap-js/consoleConnects a running CAP application to the CAP console.sap official, cap
Connects a running CAP application to the CAP console
@cap-js/data-inspector@cap-js/data-inspectorInspects database entities and their contents at the CAP service level.sap official, cap
Inspects database entities and contents at CAP service level
Local developmentSAP and community
vite-plugin-cdsvite-plugin-cdsA CAP plugin that serves a Vite app from the app folder through cds watch, makes .cds files importable into the frontend build, and can polyfill enough of Node to run @sap/cds in the browser.independent, cap
Serves a Vite app through cds watch and imports .cds files
TestingSAP and community
cds-cucumbercds-cucumberBehaviour-driven tests for CAP applications: Gherkin scenarios that drive a running service rather than assertions written against handlers.community org, cap
Gherkin scenarios driving a running CAP service
cds-launchpad-plugincds-launchpad-pluginIndexes every SAPUI5 application in a workspace into one sandbox launchpad served by the CDS server, so all of them can be opened from a single page while developing.independent, cap
Sandbox launchpad for all SAPUI5 apps in a CAP workspace
TypeScript patternsSAP and community
cap-handler-frameworkcap-handler-frameworkConvention-based handler layer for CAP: methods named beforeCreate, onRead or afterUpdate are mapped automatically, with the draft lifecycle given its own explicit hooks rather than folded into the active-entity ones.independent, cap
Convention-based handler layer for CAP with draft lifecycle hooks
cds-plugin-handlerscds-plugin-handlersA CAP plugin that structures handlers as one file per entity, in a folder per service, instead of one service implementation that keeps growing.independent, cap
One handler file per entity in CAP services
