Bundled mode

In Bundled mode, you configure walkerOS with JSON files and build standalone bundles using the CLI. The output is a separate file that can be deployed independently of your application.

Quickstart

1. Install the CLI

2. Create a flow configuration

Create flow.json:

Web (browser)
Server (Node.js)

3. Build the bundle

This writes the bundle to stdout. Use -o to write to a file:

Web: -o ./dist/walker.js (IIFE format, loadable via script tag)
Server: -o ./dist/bundle.mjs (ESM format, runnable with Node.js)

4. Deploy

Web
Server

Add to your HTML:

<script src="/walker.js"></script>

Run directly:

node ./dist/bundle.mjs

Or with Docker:

walkeros run flow.json

Adding destinations

Add destinations to your flow.json:

Rebuild: walkeros bundle flow.json

Add consent requirements in the destination config:

Set consent at runtime:

// After loading walker.js
elb('walker consent', { functional: true, analytics: true });

Key concepts

The `package:` property

In Bundled mode, you reference packages by name:

"sources": {
  "browser": {
    "package": "@walkeros/web-source-browser"
  }
}

The CLI downloads and bundles the package. This differs from Integrated mode where you use code: with a direct import.

Variables and environment

Use variables for environment-specific values:

Environment variables ($env.NAME:default) are resolved at build time. Config variables ($var.name) reference values from the variables section.

Multiple flows

Define different flows for different environments:

Build specific flow: walkeros bundle flow.json --flow production

CLI commands

Command	Purpose
`walkeros bundle`	Build production bundle
`walkeros push --simulate`	Test with mocked events
`walkeros push`	Test with real API calls
`walkeros run`	Start HTTP collection server

See CLI documentation for full details.

Docker deployment

For production server deployments:

See Docker documentation for complete deployment guides.

Next steps

CLI documentation: All CLI commands and options
Docker deployment: Production container deployment
Mapping: Transform events for destinations

Quickstart​

1. Install the CLI​

2. Create a flow configuration​

3. Build the bundle​

4. Deploy​

Adding destinations​

Adding consent​

Key concepts​

The package: property​

Variables and environment​

Multiple flows​

CLI commands​

Docker deployment​

Next steps​

See also​