Everything in CAP / Node.js
Type
Domain
Origin
Signals: 2
Content
Node.js: Answers in Node.js
More
Group by: Capability
WebSocket and Socket.IO adapter for CDS services
Spreadsheet upload into a CDS entity, parsed on the server
CAP plugin stripping whitespace from strings on write via @cds.trim
CAP plugin uppercasing strings on write via @cds.uppercase
MCP server generating tools from a CAP or OData V4 service's metadata
Developer-centric command line for SAP HANA
CAP samples generating email through SAP AI Core with anonymization
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP service kind putting eleven model providers behind one API
CAP samples using SAP AI Core's Prompt Registry for templates
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
CAP samples filling a prompt template sent to SAP AI Core
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Exposes an annotated CDS service as an Agent-to-Agent agent
No public repository is declared on the package, so the README is the documentation.
Toolkit turning a CAP service into tools for agent frameworks
Skill assessing API usage against the SAP API Policy
It says so itself, in bold, and the atlas repeats it: not legal advice and not a compliance decision. Only SAP, your contract, or SAP support can answer bindingly, and the skill routes legal, commercial and roadmap questions there rather than guessing at them. Treat the output as evidence gathered, not as a verdict.
Six CAP features in one package, from replication cache to rate limits
It is a bundle, not a plugin with one job. Depending on it for one feature brings the rest.
Shared ESLint configuration for SAPUI5 and CAP projects
ESLint rules flagging deprecated CAP configuration
Regex naming rules for SAP HANA artifacts in a CAP project
Everything it checks is a name: a file name under `rootDir`, or an identifier a parser extracted from a file, so a convention that cannot be written as a regex over one name has no rule shape here. Content rules targeting `.hdbanalyticalprivilege` or `.hdbconstraint` return no results, which the README states as not yet implemented, so conventions centred on those two artifact types go unchecked.
Decorator-driven handler registration for CAP in TypeScript
Typed BaseRepository over CAP entities
Convention-based handler layer for CAP with draft lifecycle hooks
CDS build task compiling TypeScript sources during cds build
Playback-only SAP Companion (Help4) workarea served from CAP
Not behind a managed approuter: SAP Build Work Zone does not expose the `/$companion/**` routes, so Companion never reaches CAP, and the README names managed approuter and Work Zone as out of scope for v1. Not where help has to be authored in a browser, since the editor, the producer and writes are absent and content lives in files the plugin compiles.
CAP plugin rendering UI5 views with entity data on the server
On the UI5 path what comes back is an XML view or fragment with the data already substituted, streamed as the entity's media content, rather than an HTML page — the README calls this pre-rendering, and only the Vue path produces markup. The view kept under `srv/` has its UI5 bindings replaced by Handlebars expressions, so it is a second copy of the view, separate from the one the application ships. Version 1.0.8 declares `@sap/cds` `>=8` as its peer dependency, which puts a project on CAP 7 outside its stated range.
UI5 CLI middlewares running inside the CDS server
For a deployed application's UI. The README adds it with `npm add cds-plugin-ui5 -D`, a development dependency of the CDS server, and states nothing about a build or a deployment.
MCP server searching seventeen SAP documentation repositories
It reads documentation, never a system: nothing in it opens a package.json, a CDS model or an ABAP client, so a question about what your own project does has to be answered elsewhere. The offline half is only as fresh as the submodules the last build pinned, and the index answers where something is written down rather than which of two packages fits a task.
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Financial Risk Analyzer built by an agent grounded in SAP MCP servers
Travel-booking reference app on CAP Node.js and Java backends
CAP-based PWA for EV drivers proxying SAP E-Mobility OData APIs
Event registration app showing OData V4 draft with UI5 and CAP
Todo app with CAP and SAPUI5 in TypeScript over OData V4
Neither the package manifest nor the repository tree declares a licence.