Node.js
A cross-platform JavaScript runtime that servers, command line tools and scripts written in JavaScript are run with. For the things here, the prerequisite a repository names when its build is a set of npm scripts.
Where it sits
Used by
Dependency relationship. Runs the JavaScript it writes; the transpiled ABAP and its tests execute there.
Required dependency. It is a Node command line and library, and the README names the Node version it needs.
Required dependency. Runs on Node.js 20 or newer, beside the official cf CLI that it drives.
Required dependency. Runs on Node.js 20 or newer.
Required dependency. It is a Node command line and library, and the README names the Node version it needs.
Required dependency. Runs on Node.js 20 or newer.
Required dependency. Runs on Node.js 20 or newer, with the official cf CLI on the path.
Dependency relationship. The command line and its API run on Node.js 20 or later, beside the official cf CLI on the path.
Required dependency. It is a Node command line and library, and the README names the Node version it needs beside the cf CLI on the PATH.
Dependency relationship. The command line runs on Node.js 20 or later, beside the official cf CLI on the path.
Required dependency. It is a Node command line and library, and the README names the Node version it needs beside the cf CLI on the PATH.
Required dependency. It is a Node command line and library, and the README names the Node version it needs.
Required dependency. The transpiled ABAP and the ABAP Unit tests run as a Node process, both on a developer's machine and in the CI job the scaffold installs.
Functional boundary
Not a substitute for testing in a system: the README states that any class calling the database, classic BAPIs or HTTP is shimmed out and stays an on-stack ATC and ABAP Unit concern, and that an off-stack green is CI-grade provenance rather than an in-system pass. It also assumes a particular shape of project. The ABAP has to be abapGit-serialised into a Git repository, Node.js 22 or later has to be available locally and in CI, and the CI has to be GitHub Actions.
Required dependency. the runtime for the npm scripts and Grunt tasks that download, unzip and package the bundle
Dependency relationship. The MCP client starts the server as a Node process from the built output, and the repository names the runtime version it is built and run with.
Functional boundary
Any run nobody is watching: the drawing tools work only while the draw.io canvas at `http://localhost:3000/` is open and connected, so there is no diagram to produce on a build agent or a server. Nothing checks the result either, because the maintainer keeps a diagram linter on the [roadmap](https://github.com/etosin/arc-draw#-roadmap) rather than in the release. The maintainer marks the status early at v0.x, installs it from source, and records testing with Claude Code alone.
Required dependency. the runtime the generator is installed into and run on, at the version the requirements name
Required dependency. installing the dependencies and running the npm build of each sample before it is deployed
Required dependency. The detection script and every scaffolding command run through Node and npm on the developer's own machine.
Functional boundary
Local scaffolding only. Its own Out of Scope list names deployment to Cloud Foundry or Kyma, XSUAA and IAS configuration or any other BTP service binding, the SaaS Registry and subscription flow to real tenants, and automatic migration from the legacy `@sap/cds-mtx`. For the concepts rather than the scaffolding step, the README points at the `multitenancy` skill in [skillOverflow](artifact:dankromp-skilloverflow) by [Daniel Krompaß](actor:dankromp), which covers the MTX sidecar, `xs-security.json`, tenant lifecycle hooks and the deployment path and runs no commands at all.
Required dependency. the runtime the application is installed and started on, at the version the Requirements name
Dependency relationship. Running the CAP backend and the React frontend, at version 18 or higher as the README's prerequisites state.
LicenceNeither the package manifest nor the repository tree declares a licence
Required dependency. the runtime the transpiled ABAP and its unit tests execute on, and the runner for every npm script the README documents
Dependency relationship. The transpiled code that calls these classes runs there.
Optionally used: it is run locally, outside an ABAP system running it and its tests locally, with NodeJS 16 or later
Required dependency. the local installation development needs, an active LTS version with its supported npm.
Dependency relationship. The runtime the MCP server runs on, shipped inside the Windows installer rather than installed separately.
Optionally used: the RFC tools are used The RFC half runs through a Node bridge on the open-rfc package; the OData and TED tools run on Python alone.
Functional boundary
On ECC the S/4HANA `API_*` services that the three convenience readers default to do not exist, so each one has to be pointed at a Z service of your own or replaced by the RFC tools. `read_table` inherits `RFC_READ_TABLE`'s 512-byte row, so a wide table needs an explicit field list and some fields cannot be selected at all, and the bridge starts a Node process and a fresh logon per call, with no pooling. The audit log is one line per call that includes the call arguments, so every filter and WHERE clause sent to SAP is written to a file that then has to be handled as sensitive.
Required dependency. building the React frontend before the server is started
Required dependency. The registered server is started with npx from the hana-cli npm package, which the README lists Node.jsNode.jsA cross-platform JavaScript runtime that servers, command line tools and scripts written in JavaScript are run with. For the things here, the prerequisite a repository names when its build is a set of npm scripts. 20.19.0 or later for.
Dependency relationship. one of the few things the exercises need on the machine, at the version the README names; the session's machine has it installed already.
Dependency relationship. The runner is a Node command line installed from npm into the tested project or globally, and the README names the Node version it works with.
Dependency relationship. running the UI5 dev server every exercise scans the live app on; the README pins the versions it expects.
Dependency relationship. running the UI5 dev server and the OData V4 data service the starter ships; the README pins the versions it expects.
Dependency relationship. the source-based macOS setup, which requires version 22.12 or newer
Details
Graph
For your agent
- Ref
external:nodejs- JSON
- /externals/nodejs.json
- MCP
- Connecting an agent