For the complete documentation index, see llms.txt. This page is also available as Markdown.

Downloading the Node.js Agent

The SeaLights Node.js agent is published in the npm registry and installed with npm. There is no separate binary to download.

Using an internal artifact repository? If your organization mirrors npm packages through Artifactory, Nexus, or another private registry, install slnodejs from that registry instead. The package name and version syntax stay the same.

Choosing an installation strategy

There are two ways to control which version to install:

Strategy
When to use

Latest

Quick start, dev environments, and POCs

Specific version

Production pipelines — resolve from API or pin explicitly

Strategy 1: Install the latest version

This installs the newest published release at runtime. Use it when you want the latest features and can tolerate version changes between runs.

echo "[SeaLights] Installing Node.js agent (latest)..."
npm install slnodejs@latest
npm ls slnodejs --depth=0
- name: Install SeaLights Node.js Agent (latest)
  run: |
    echo "[SeaLights] Installing Node.js agent (latest)..."
    npm install slnodejs@latest
    npm ls slnodejs --depth=0
Write-Host "[SeaLights] Installing Node.js agent (latest)..."
npm install slnodejs@latest
npm ls slnodejs --depth=0
- script: |
    echo "[SeaLights] Installing Node.js agent (latest)..."
    npm install slnodejs@latest
    npm ls slnodejs --depth=0
  displayName: Install SeaLights Node.js Agent (latest)

Use this strategy in production pipelines. It gives you stable installs and controlled upgrades.

Choose one of these approaches:

  • Installer utility — simplest path. It resolves and installs the approved version for you.

  • Explicit version management — no extra package. You control the API call and npm install flow directly.

Approach 1: Installer utility

Use this when you want the approved version from the Dashboard without managing the resolution logic yourself.

To run the installer, provide your SeaLights Agent Token either in sltoken.txt at the project root or as the SL_TOKEN environment variable.

The installer authenticates with your token, resolves the approved version from the Dashboard, installs that exact slnodejs release, and writes install.log for troubleshooting.

Approach 2: Explicit version management

Use this when you do not want to install an additional package or when you want full control over the commands in your pipeline.

Tip: Leave SL_AGENT_VERSION empty in the snippets below to resolve the approved version from the Dashboard automatically.

  • When the approved version changes, pipelines pick it up on the next run.

  • When troubleshooting, set it to latest or pin it to X.Y.Z.

API endpoint

  • Authentication: Authorization: Bearer <your-agent-token>

  • Response: JSON object with a version field, for example {"version": "4.2.1"}

Last updated

Was this helpful?