Everything in CAP / Node.js
Type
Domain: 2
Origin
Signals
Content
Node.js: Answers in Node.js
More
Group by: Kind
Compares a CAP project's CSV data with its database rows
Interactive generator for CAP event handler files
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.
Test support for CAP Node.js: server start, HTTP client, assertions
Generates TypeScript types from a CDS model
Type definitions for the CAP Node.js SDK
Connects a running CAP application to the CAP console
Inspects database entities and contents at CAP service level
Placeholder package under a CAP annotations name, no annotations
The manifest calls it a dummy library exposing custom CDS annotations, but the published contents are a one-line README, a single exported barrier() whose body is throw Error("not yet implemented"), and no .cds file at all — there is nothing to import and nothing to annotate with. No repository, one release, May 2025.
Shared ESLint configuration for SAPUI5 and CAP projects
Decorator-driven handler registration for CAP in TypeScript
Typed BaseRepository over CAP entities
Interactive project installer for CAP Node.js
CLI starting several CAP services and an AppRouter locally together
CLI of CAP development tools for Cloud Foundry workflows
There is no repository and no README: what the eight commands do is only readable from the compiled dist that ships in the package. Three of them — npmrc, install, project — are written for "SimpleMDG" projects rather than for CAP generally, so the reusable part is bind-local, run-local and debug. Seven releases up to July 2026. Its binding step writes the resolved VCAP_SERVICES into default-env.json in the project, where [@sap/cds-dk](artifact:sap-cds-dk) keeps only the place the credentials can be fetched from, so a project using it needs that file kept out of version control.
Command line for changing features of an existing Fiori project
Writer of flexible programming model elements into Fiori elements apps
Writer that adds an OData service to an existing UI5 project
Compiler from AMS DCL policies to DCN for local runs and tests
Its own account of itself is local running and tests: the DCN it writes serves as input for running an application using AMS on the DCL bundle locally. It carries the SAP Developer License Agreement rather than an open-source licence, and the repository named in its package metadata is an internal SAP host, so the npm page is the only thing to read.
CAP Node.js runtime
ISO content for CAP's countries, languages, currencies and timezones
Command line client and development toolkit for CAP
OData annotation features for the @sap/vscode-cds extension
Endpoint discovery for CAP services deployed to Cloud Foundry
Workspace-wide CSN cache for querying CAP entities and columns
Static end-to-end tracer of one CAP operation across repositories
Groups npm audit findings by root dependency, with failing thresholds
It audits through npm: a project that resolves its dependencies with another package manager, or has no `package.json`, has nothing for it to run. What it reports is what `npm audit` knows, so a vulnerability outside the npm advisory data is not in its table.
Convention-based handler layer for CAP with draft lifecycle hooks
CSV seed data generated from @Mockdata annotations with Faker
Quiet Release and repository quiet for 27 months.
Functional boundary Not a test-data factory. It writes files at build time to seed a database, so it does not build fixtures inside a unit test. The declared peer range stops at cds 7 — nothing says it fails on 9, but nothing says it was tried either.
Fills db/data with relationally consistent CSV from a .cds schema
npx tool adding worked example files to a CAP project
Last released April 2024.
Gherkin scenarios driving a running CAP service
Typed class-based service layer over CAP ApplicationService
Last released July 2022, and no repository is declared on the package.
Reusable internals for authors of CAP extensions
Explicitly internal utilities, so the surface is not a stable public API and last moved in March 2024. The repository the package declares has been deleted — verified against the GitHub API, not just a failed fetch. The package is still on npm, so it installs; the source it was published from is no longer readable, which is a harder thing to discover than a stale version number.
Sandbox launchpad for all SAPUI5 apps in a CAP workspace
One handler file per entity in CAP services
CDS build task compiling TypeScript sources during cds build
Decorator-based routing of CAP service handlers in TypeScript
Release and repository quiet for 46 months.
TextMate grammar for the CDS language
Not an editor integration. If you want completion, navigation and diagnostics, that is the CDS language server, not this.
CLI generating TypeScript interfaces from a CDS model
Hosted workspace redrawing custom ABAP as BPMN and grading it
Not reachable Not reachable since 2026-10-20.
Functional boundary The Level A–D grade merges SAP's two published files in the tool's own engine: it is an orientation rather than an ATC result and is left out of the signed audit pack, and the repository documents state by state where the grade is expected to differ from what the clean core ATC check reports. Nothing here runs ABAP Unit — on the RAP track that result is recorded from your own SAP system, and generated CAP tests run against mocks in an isolated runner rather than in a real SAP S/4HANA system. Tenants, organisation accounts, single sign-on, a self-hosted edition and write access through an API are deliberately not built, and one account has five analysis runs before a Gemini API key of its own is needed.
Static check that each exported TypeScript function has a test
It reads TypeScript exports only; a project written in plain JavaScript has no exported functions for it to extract. A call to the function name in a test file counts as tested, and a call through property access such as `.foo(` does not.
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.
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.
Development environment on BTP for UI5, Fiori, mobile and CAP
Predefined CI/CD pipelines for SAP development projects
Attaches a debugger to a CAP app running on Cloud Foundry
AWK script sketching an ER diagram from .cds files
No published releases; repository quiet for 26 months.
Terminal UI running Bruno collections against a CAP service
UI5 app consuming the cds-bookshop server via ui5-middleware-cap
Serves a Vite app through cds watch and imports .cds files
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
CAP service in TypeScript using types from @cap-js/cds-typer
CAP project built and deployed to Cloud Foundry by GitHub Actions
CAP Java service consuming a Business Partner API mocked in Node.js
Neither the package manifest nor the repository tree declares a licence.
CAP sample drawing a material BOM as a UI5 network graph
Neither the package manifest nor the repository tree declares a licence.
Development container definition for CAP Node.js
Chat app on CAP and SAPUI5 against the OpenAI API
It calls the OpenAI API directly with a key in the environment. It was written in early 2023 and last touched in May 2023, which is before SAP AI Core and the CAP LLM plugins existed — so read it for the shape of the application, not for how a CAP service should reach a model today.
CAP project simulating S/4HANA Private Edition OData APIs locally
Financial Risk Analyzer built by an agent grounded in SAP MCP servers
reCAP 2025 workshop on CAP's local-development toolset
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.
pnpm workspace running CAP, a local launchpad and two UI5 apps
Neither the package manifest nor the repository tree declares a licence.