CDS pluginCDS plugintypeInstalls into a CAP project and extends the runtime. CAP loads it through cds.requires or the plugin hook.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 →

cds-launchpad-plugin

Indexes 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.

Facts

Latestv2.3.0ReleasedLast pushLicenceMIT

Where it sits

Lives in
Provides
TestingCAPTestingcapabilityProving the service still does what it did — against the model and the handlers, without a deployed system and without a database somebody has to keep clean.
Flavors
Requires
@sap/cds≥ 5@sap/cdsartifactThe peer range, as published.

Who is behind it

Geert-Jan KlapsGeert-Jan KlapsPersonMaintains this
In the atlas: maintains 4, contributes to 11, wrote 4
@geert-janklaps
maintainerCarl ÖnnheimPersonContributes to this
In the atlas: contributes to 1
@carlonnheim
corporateuserPersonContributes to this
In the atlas: contributes to 3
@corporateuser
Austin DevinePersonContributes to this
In the atlas: maintains 7, contributes to 25
@devinea
EGnedelPersonContributes to this
In the atlas: contributes to 1
@EGnedel
GoWalePersonContributes to this
In the atlas: contributes to 2
@GoWale
Gregor WolfPersonContributes to this
In the atlas: maintains 17, contributes to 59, wrote 2
@gregorwolf
kingagesPersonContributes to this
In the atlas: contributes to 1
@kingages
Marian ZeisPersonContributes to this
In the atlas: maintains 35, contributes to 86, wrote 25
@marianfoo
Dennis EisoldPersonContributes to this
In the atlas: contributes to 1
@mcules
Nils SchnabelPersonContributes to this
In the atlas: contributes to 8
@nils
12 contributors

Before choosing this

Conditions

LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2, 3A cds-plugin is used with SAP CAP materials, or an artifact is explicitly identified as a CAP plugin or application.
  • § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
  • § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.
  • § 3 Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
SAP Developer License Agreement 3.2 CAP →

What it declares

Every artifact

Type
CDS plugin
Origin
Independently maintained

As a CDS plugin

Declared for
>=5
Distributed through
npm

Tasks this contributes to1Beta

Reach every UI app of a CAP project from one page while developingA 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.Node.jsAssessed, not knownsandbox launchpad
What it does

A cds-plugin that serves a launchpad from the CDS server for demo, development and testing. How it finds the applications it lists is not stated in the README read here, so whether it answers this outcome for a project's own apps without further configuration is not established.

Remaining work

Read the plugin's configuration options, appConfigPath among them, before treating a project's apps as listed by it. Its edge in the graph points at capability:testing rather than at this capability, and that placement has not been examined either.

All options on the Integrated frontend dev server page →

Connections1

cds-launchpad-plugin connectionscds-launchpad-pluginPROVIDES→ provides1provides authoredTesting

Install

npm add cds-launchpad-plugin

Derived from the package name. No recipe recorded; the README has the configuration.

Learn more3

Readings
  1. cds-launchpad-plugin supercharged & ready for the future - CAP Plugin, UI5 Tooling support & Async LaunchpadGeert-Jan Klaps, SAP Community
  2. A Fiori Launchpad Sandbox for all your CAP-based projects - OverviewGeert-Jan Klaps, SAP Community
  3. A Fiori Launchpad Sandbox for all your CAP-based projects – Sample project setupGeert-Jan Klaps, SAP Community

README

quoted from geert-janklaps/cds-launchpad-plugin under MIT, read
geert-janklaps/cds-launchpad-plugin/README.mdOn GitHub

cds-launchpad-plugin

Launchpad Plugin for demo / development / testing SAP Cloud Application Programming Model-based projects

Installation

In your project, run following command:

npm install --save-dev cds-launchpad-plugin

Usage

SAP Cloud Application Programming (CAP) Model 6.7.0 or higher

The cds-launchpad-plugin is using the SAP Cloud Application Programming Model plugin technique. Installing the plugin as a dev dependency (see installation) is sufficient to enable the plugin automatically.

Configuration

Optionally you can configure the cds-launchpad-plugin by adding following configuration to your package.json file.

"cds": {
  "launchpad": {
    "theme":"sap_horizon", // SAPUI5 Theme
    "version": "1.120.1", // SAPUI5 Version
    "basePath": "", // Path under which you want the sandbox to be served
    "appConfigPath": "", // External sandbox appconfig json file to be merged with generated appconfig
    "locale": "", // Language to be used for the sandbox environment
    "template": "" ,// 'legacy' (non-async launchpad, default) or 'async' (async launchpad),
    "modulePaths": "" // object with module paths to be used in the launchpad.html file for "sap-ushell-config"
  }
}

The sandbox launchpad will be served on /$launchpad, like http://localhost:4004/$launchpad

SAP Cloud Application Programming (CAP) Model 6.7.0 or lower

Have this in your server.js:

const cds = require ('@sap/cds');

/* For releases before cds 7:
replace:
cds.env.production === false
with:
process.env.NODE_ENV !== 'production'
*/
if (cds.env.production === false){
    const {cds_launchpad_plugin} = require('cds-launchpad-plugin');

    // Enable launchpad plugin
    cds.once('bootstrap',(app)=>{
        const handler = new cds_launchpad_plugin();
        app.use(handler.setup({theme:'sap_horizon', version: '1.120.1'}));
    });
}

The sandbox launchpad will be served on /$launchpad, like http://localhost:4004/$launchpad

Configuration

Call setup({...}) method with the following object (configuration object can be omitted):

{
  theme:'sap_horizon', // SAPUI5 Theme
  version: '1.99.0', // SAPUI5 Version
  basePath: '', // Path under which you want the sandbox to be served
  appConfigPath: '', // External sandbox appconfig json file to be merged with generated appconfig
  locale: '', // Language to be used for the sandbox environment
  template: '', // 'legacy' (non-async launchpad) or 'async' (async launchpad)
  modulePaths: '' // object with module paths to be used in the launchpad.html file for "sap-ushell-config"
}

External references

Solution overview: https://blogs.sap.com/2022/03/14/a-fiori-launchpad-sandbox-for-all-your-cap-based-projects-overview/

Sample project setup: https://blogs.sap.com/2022/03/14/a-fiori-launchpad-sandbox-for-all-your-cap-based-projects-sample-project-setup/

Development

Prerequisites
  • node 18
  • pnpm
Setup
git clone https://github.com/geert-janklaps/cds-launchpad-plugin
cd cds-launchpad-plugin
pnpm install
pnpm watch
# run cds server
pnpm dev:sapux
# go to http://localhost:4004/$launchpad
MIT, read

History

Latest

v2.2.0

Features 1

Notes
Features
  • define modulePaths in launchpad.html file (#44) (3a5429d)
  1. v2.1.8

    Fixes 1

    Notes
    Bug Fixes
    • basepath as default page issue with search parameters (a72f5c2)
  2. v2.1.7

    Fixes 1

    Notes
    Bug Fixes
    • only use apps from deps if cds-plugin-ui5 is present (#35) (41be0e2)
541downloads per week, npm
Weekly downloads for cds-launchpad-plugin26 complete calendar weeks from 2026-04-27 to 2026-10-25; the latest total is 541.27 Apr – 3 May: 2,5094 May – 10 May: 2,19211 May – 17 May: 1,53118 May – 24 May: 1,99825 May – 31 May: 1,8921 Jun – 7 Jun: 1,7968 Jun – 14 Jun: 2,08715 Jun – 21 Jun: 2,24422 Jun – 28 Jun: 2,36429 Jun – 5 Jul: 2,4546 Jul – 12 Jul: 2,74013 Jul – 19 Jul: 5,54920 Jul – 26 Jul: 7,42427 Jul – 2 Aug: 2,3223 Aug – 9 Aug: 2,30610 Aug – 16 Aug: 2,41817 Aug – 23 Aug: 2,61224 Aug – 30 Aug: 1,98631 Aug – 6 Sept: 1,5917 Sept – 13 Sept: 1,53214 Sept – 20 Sept: 1,87321 Sept – 27 Sept: 2,62628 Sept – 4 Oct: 2,7345 Oct – 11 Oct: 2,96212 Oct – 18 Oct: 1,29519 Oct – 25 Oct: 541
Testing
  1. com.sap.cds:cds-services-bomMaven bill of materials pinning CAP Java module versionsfrom CAP
  2. @cap-js/cds-testTest support for CAP Node.js: server start, HTTP client, assertionsfrom CAP
  3. cds-cucumberGherkin scenarios driving a running CAP servicefrom CAP
  4. sapbrunoTerminal UI running Bruno collections against a CAP servicefrom CAP
  5. enforce-export-coverageStatic check that each exported TypeScript function has a testfrom General
  6. @sap-ux/fe-mockserver-plugin-cdsFiori Elements mock server plugin taking a CDS file as metadatafrom CAP
  7. @saptools/brunoRunner for Bruno collections against XSUAA-protected CF appsfrom BTP/BAIP

Details

Sources5
npm registrydiscovered herechecked
The discovery passdiscovered herechecked
npm registry, cds-launchpad-pluginversion, releases, installschecked
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
declared for>=5
latestv2.3.0
first release
releases and cadence22, ~4d median
discovered vianpm registry, The discovery pass
first seen in the atlas
ecosystem and domaincap, developer-experience
Flavors1
Node.js
“npm install --save-dev cds-launchpad-plugin” — geert-janklaps/cds-launchpad-plugin — READMEchecked
Contributors12
History in the atlas2
  1. Indexes 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.
  2. First seen.
For your agent
Ref
artifact:geert-janklaps-cds-launchpad-plugin
JSON
/artifacts/geert-janklaps-cds-launchpad-plugin.json
MCP
Connecting an agent