onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
CLICLItypeA command you run, rather than a dependency you import.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 →

@sang2x/captools

A CLI of eight CAP development commands aimed at Cloud Foundry workflows, shipped without a repository or README, whose binding step writes resolved VCAP_SERVICES into default-env.json.

npm3/wk

Facts

Latestv0.8.0ReleasedLicenceMIT

Where it sits

Lives in
CAP
Provides
Local developmentCAPLocal developmentcapabilityRunning the whole stack on a laptop against real bindings — the service, the UI and the routing in front of it — without deploying to see a change.
Flavors
Node.jsJavafrom its runtime
Runs
Cloud Foundry

Who is behind it

sang2x

Before choosing this

Conditions

PracticalFunctional boundary

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 keeps only the place the credentials can be fetched from, so a project using it needs that file kept out of version control.

What it declares

Every artifact

Type
CLI
Origin
Independently maintained
Runtime
build time
Runs on
Cloud Foundry

As a CLI

Distributed through
does not say

For local development

Supports
Binds cloud servicesCredentials on disk
Part of the local stack it starts
CAP service
property statedstated nonot said

Tasks this contributes to1Beta

Local development1
Run a CAP service against a cloud service instanceA service running on a laptop reads and writes through a service instance that exists in the cloud — a database, a destination, an authentication service — instead of through the local substitute, with nothing deployed.Node.js, JavaCovers, under conditionsthe binding and the run behind one command
What it does

bind-local binds the local project to the services of a Cloud Foundry application and writes the resulting VCAP_SERVICES into default-env.json; run-local chains that behind one command with the install step and cds watch --profile hybrid.

Conditions

the target is a Cloud Foundry space with the application already deployed, since the command reads the bound services of an app; the resolved VCAP_SERVICES may be written into default-env.json in the project

Remaining work

Keep the written file out of the repository, and read the published dist to know what a command does: there is no repository and no README.

All options on the Local development page →

Connections1

Install

npm add @sang2x/captools

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

History

Latest

v0.8.0

  1. v0.7.0

  2. v0.6.0

  3. v0.5.0

  4. v0.4.0

  5. v0.3.0

  6. v0.2.0

  7. v0.1.0

On npm
2downloads per week, npm
Weekly downloads for @sang2x/captools26 complete calendar weeks from 2026-04-20 to 2026-10-18; the latest total is 2.20 Apr – 26 Apr: 027 Apr – 3 May: 04 May – 10 May: 011 May – 17 May: 018 May – 24 May: 025 May – 31 May: 01 Jun – 7 Jun: 08 Jun – 14 Jun: 015 Jun – 21 Jun: 72222 Jun – 28 Jun: 17429 Jun – 5 Jul: 1906 Jul – 12 Jul: 3313 Jul – 19 Jul: 1220 Jul – 26 Jul: 2127 Jul – 2 Aug: 43 Aug – 9 Aug: 2910 Aug – 16 Aug: 3017 Aug – 23 Aug: 324 Aug – 30 Aug: 931 Aug – 6 Sept: 147 Sept – 13 Sept: 1414 Sept – 20 Sept: 321 Sept – 27 Sept: 228 Sept – 4 Oct: 1885 Oct – 11 Oct: 412 Oct – 18 Oct: 2

Others providing9

Compare all 10 on the Local development page →
Local development
  1. vite-plugin-cdsServes a Vite app through cds watch and imports .cds files
  2. com.sap.cds:cds-feature-dev-dashboardBrowser dashboard for a running CAP Java service during development
  3. com.sap.cds:cds-maven-pluginMaven plugin running CDS build steps in a CAP Java project
  4. @cap-js-community/commonSix CAP features in one package, from replication cache to rate limits
  5. @neoimpulse/cap-js-bootstrapCLI starting several CAP services and an AppRouter locally together
  6. @sap/ams-devCompiler from AMS DCL policies to DCN for local runs and tests
  7. @sap/cds-dkCommand line client and development toolkit for CAP
  8. @sap/cdsCAP Node.js runtime
  9. dev-approuterDev-time wrapper for the SAP Application Router

Details

Sources2
npm registrydiscovered here, keywords:cdschecked
npm registry, @sang2x/captoolsversion, releases, installschecked

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
runtimesbuild-time
deploymentCloud Foundry
latestv0.8.0
first release
releases and cadence8, ~1d median
discovered vianpm registry · keywords:cds
first seen in the atlas
ecosystem and domaincap, developer-experience
History in the atlas2
  1. The three comparison values this capability declares, and the sentence about where the credentials land.
  2. First seen.
For your agent
Ref
artifact:sang2x-captools
JSON
/artifacts/sang2x-captools.json
MCP
Connecting an agent