Everything in CAP / Node.js
Type
Domain: Operations & Runtime
Origin
Signals
Node.js: Answers in Node.js
More: 2
Group by: Capability
Shows which feature branches reached which environment branch
A team that does not keep one long-lived branch per environment has no environment branches for it to compare feature branches against. What it reports is the merge state of branches in Git, so it says nothing about whether a merged change has been built or deployed to the environment.
Tool completing a CAP project's deployment configuration
Tied to a specific training repository and last released August 2023. 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.
Switches Cloud Foundry API, org and space from a view in VS Code
MTA deploying CAP, HDI container and a Fiori elements app
CAP plugin controlling CDS logger and OpenTelemetry log verbosity
Policy enforcement and field masking for MCP-enabled CAP apps
CAP caching plugin for query results and remote service responses
When user-dependent responses are cached without user-aware or explicit operation keys, or translated responses share keys across locales. These cases require key isolation; locale-aware keys are off by default.
CAP plugin joining external entities with internal tables at query
The declared repository is on SAP's internal GitHub (github.tools.sap) and is not publicly reachable, so npm is the only place to read anything about it.