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 →

@neoimpulse/cap-js-bootstrap

A command-line tool that starts a local CAP environment with several services and an AppRouter together from one command, documented in German and requiring Node 22 or newer.

The multi-service case, where cds watch serves one project and the router has to be started beside it by hand. Documented in German, and it requires Node 22 or newer.

npm3/wk

Facts

Latestv1.1.2ReleasedLicenceMIT License

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.jsfrom its runtime

Who is behind it

neoimpulse GmbHneoimpulse GmbHOrganisationMaintains this
In the atlas: maintains 7@neoimpulseGmbHmaintainer

What it declares

Every artifact

Type
CLI
Origin
Independently maintained
Runtime
Node.js

As a CLI

Distributed through
does not say

For local development

Part of the local stack it starts
CAP serviceApp Router

Tasks this contributes to1Beta

Local development1
Open a CAP application through its router locallyA developer opens the application on a laptop at the address the App Router serves, logs in through the real authentication flow, and reaches the CAP service and the UI modules behind it the way a deployed request would.Node.jsCovers, under conditionsseveral services and the router from one command
What it does

Starts a local CAP development environment of several services together with the App Router: cds watch per service, sequentially or in parallel, and the router through cds bind --exec -- npm start.

Conditions

Node.js 22 or newer, which the package states as its requirement; a binding the router's own start command can resolve, since it starts the router through cds bind --exec

Remaining work

Configure the services it is to start. The documentation is in German, and the repository declared in the package metadata returns 404, so the npm page is the only thing to read.

All options on the Local development page →

Connections1

Install

npm add @neoimpulse/cap-js-bootstrap

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

History

Latest

v1.1.2

  1. v1.1.1

  2. v1.0.9

  3. v1.0.8

  4. v1.0.7

  5. v1.0.6

On npm
0downloads per week, npm
Weekly downloads for @neoimpulse/cap-js-bootstrap26 complete calendar weeks from 2026-04-27 to 2026-10-25; the latest total is 0.27 Apr – 3 May: 64 May – 10 May: 1811 May – 17 May: 1118 May – 24 May: 30425 May – 31 May: 141 Jun – 7 Jun: 168 Jun – 14 Jun: 1215 Jun – 21 Jun: 5022 Jun – 28 Jun: 7129 Jun – 5 Jul: 256 Jul – 12 Jul: 1313 Jul – 19 Jul: 1720 Jul – 26 Jul: 2427 Jul – 2 Aug: 33 Aug – 9 Aug: 1210 Aug – 16 Aug: 1417 Aug – 23 Aug: 2024 Aug – 30 Aug: 11231 Aug – 6 Sept: 137 Sept – 13 Sept: 814 Sept – 20 Sept: 321 Sept – 27 Sept: 628 Sept – 4 Oct: 75 Oct – 11 Oct: 112 Oct – 18 Oct: 319 Oct – 25 Oct: 0

Others providing14

Compare all 15 on the Local development page →
Local development
  1. abap2UI5 PlaygroundIn-browser ABAP editor beside the abap2UI5 app it buildsfrom ABAP
  2. web-abap2UI5abap2UI5 transpiled to JavaScript and run in a browser tabfrom ABAP
  3. vite-plugin-cdsServes a Vite app through cds watch and imports .cds filesfrom CAP
  4. com.sap.cds:cds-feature-dev-dashboardBrowser dashboard for a running CAP Java service during developmentfrom CAP
  5. com.sap.cds:cds-maven-pluginMaven plugin running CDS build steps in a CAP Java projectfrom CAP
  6. @cap-js-community/commonSix CAP features in one package, from replication cache to rate limitsfrom CAP
  7. abap_trial_dockerScripts running the ABAP Developer Edition in Dockerfrom ABAP
  8. open-steamgateLocal ABAP server serving /IWBEP/ OData v2 without an SAP systemfrom ABAP
  9. pokrakam/abapDevSysInitABAP report setting up a new ABAP Developer Edition or trial systemfrom ABAP
  10. @sang2x/captoolsCLI of CAP development tools for Cloud Foundry workflowsfrom CAP
  11. @sap/ams-devCompiler from AMS DCL policies to DCN for local runs and testsfrom CAP
  12. @sap/cds-dkCommand line client and development toolkit for CAPfrom CAP
  13. @sap/cdsCAP Node.js runtimefrom CAP
  14. dev-approuterDev-time wrapper for the SAP Application Routerfrom CAP

Details

Sources3
npm registrydiscovered here, cds-pluginchecked
npm registrydiscovered here, @cap-jschecked
npm registry, @neoimpulse/cap-js-bootstrapversion, 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
runtimesnode
latestv1.1.2
first release
releases and cadence6, ~0d median
discovered vianpm registry · cds-plugin, npm registry · @cap-js
first seen in the atlas
ecosystem and domaincap, developer-experience
History in the atlas3
  1. The edge with what it does, its sources and the comparison value for the parts of the local stack it starts.
  2. npm only
  3. First seen.
For your agent
Ref
artifact:neoimpulse-cap-js-bootstrap
JSON
/artifacts/neoimpulse-cap-js-bootstrap.json
MCP
Connecting an agent