CapabilityDeveloper ExperienceNode.js, read from its artifacts

Plugin authoring

Writing a package that extends the CAP runtime rather than an application that uses it — the mechanism underneath every cds-plugin in this atlas, and the question you arrive at once solving a problem twice makes you want to solve it once for everyone.

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

Overview

SAP SHIPS

@sap/cds-dk

Runs the build plugins a package registers with cds.build from its cds-plugin.js as part of cds build, and takes a build task type the plugin contributes to the cds schema.

SourceImplement Build Plugins — capirechecked 2026-09-27

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

Licence1

LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2AlwaysA plugin is developed or distributed for use with SAP CAP materials covered by the agreement.

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

The agreement expressly includes plug-ins among the SAP materials and section 2 addresses making APIs and tools available to third parties. A plugin's own open-source licence does not erase those separate use terms.

SAP Developer License Agreement 3.2 CAP →

SourceSAP Developer License Agreement 3.2 CAPchecked 2026-09-16