@walkeros/cli 0.7.0-next.0 → 1.0.0

package/CHANGELOG.md

@@ -1,159 +1,16 @@
 # @walkeros/cli
 
-## 0.7.0-next.0
+## 1.0.0
 
-### Minor Changes
+### Major Changes
 
-- 42d06c8: Fix Docker runtime version display - versions now read reliably from
-  package.json at runtime instead of fragile build-time injection
+- 67c9e1d: Hello World! walkerOS v1.0.0
 
-### Patch Changes
-
-- Updated dependencies [42d06c8]
-  - @walkeros/docker@0.7.0-next.0
-
-## 0.5.1-next.1
-
-### Patch Changes
-
-- 71b615f: Fix URL handling in resolveAsset - URLs are now passed through
-  unchanged instead of being mangled into invalid filesystem paths
-
-## 0.5.1-next.0
-
-### Patch Changes
-
-- Updated dependencies [5163b01]
-  - @walkeros/core@0.5.1-next.0
-  - @walkeros/docker@0.3.1-next.0
-  - @walkeros/server-core@0.5.1-next.0
-
-## 0.5.0
-
-### Minor Changes
-
-- just flow
-
-### Patch Changes
-
-- Updated dependencies
-  - @walkeros/core@0.5.0
-  - @walkeros/docker@0.3.0
-  - @walkeros/server-core@0.5.0
-
-## 0.4.2
-
-### Patch Changes
-
-- simulate server and local packages
-- cli cache
-- Updated dependencies
-- Updated dependencies
-- Updated dependencies
-  - @walkeros/core@0.4.2
-  - @walkeros/docker@0.2.2
-  - @walkeros/server-core@0.4.2
-
-## 0.4.1
-
-### Patch Changes
-
-- dev entry
-- Updated dependencies
-  - @walkeros/server-core@0.4.1
-  - @walkeros/docker@0.2.1
-  - @walkeros/core@0.4.1
-
-## 0.4.0
-
-### Minor Changes
-
-- Consolidate schemas and examples under `/dev` export
-
-### Patch Changes
-
-- Updated dependencies
-  - @walkeros/docker@0.2.0
-  - @walkeros/core@0.4.0
-
-## 0.3.6
-
-### Patch Changes
-
-- port path and name
-- df4b2a1: Read CLI version dynamically from package.json instead of hardcoded
-  value
-- Updated dependencies
-  - @walkeros/docker@0.1.5
-
-## 0.3.5
-
-### Patch Changes
-
-- cli usage
-- Updated dependencies
-  - @walkeros/docker@0.1.4
-
-## 0.3.4
-
-### Patch Changes
-
-- main module exec
-
-## 0.3.3
-
-### Patch Changes
-
-- force local
-
-## 0.3.2
-
-### Patch Changes
-
-- walkeros cli with docker
-- Updated dependencies
-  - @walkeros/docker@0.1.2
-
-## 0.3.1
-
-### Patch Changes
-
-- 25f7e10: Fix bundle command template path resolution to support relative paths
-
-  **CLI Changes:**
-  - Template paths starting with `./` or `../` in config files are now resolved
-    relative to the config file's directory
-  - Maintains backward compatibility for other relative paths (resolved from
-    cwd)
-  - Enables portable flow configs that reference templates next to them
-
-  **Docker Changes:**
-  - Updated demo.json and express-console.json to include template and output
-    fields
-  - Flow files can now be bundled standalone using the CLI bundle command
-  - Templates are referenced using `../templates/base.hbs` relative to flow file
-
-  **Example:**
-
-  ```bash
-  # Now works from any directory
-  node dist/index.mjs bundle -c packages/docker/flows/demo.json
-  ```
-
-- hello
-- Updated dependencies [25f7e10]
-- Updated dependencies
-- Updated dependencies
-  - @walkeros/docker@0.1.1
-  - @walkeros/core@0.3.1
-
-## 0.2.0
-
-### Minor Changes
-
-- env
+  Open-source event data collection. Collect event data for digital analytics in
+  a unified and privacy-centric way.
 
 ### Patch Changes
 
-- Updated dependencies
-  - @walkeros/core@0.2.0
+- Updated dependencies [67c9e1d]
+  - @walkeros/core@1.0.0
+  - @walkeros/server-core@1.0.0

package/README.md

@@ -14,6 +14,21 @@ The walkerOS CLI is a developer tool that:
 Think of it as your development toolchain for walkerOS - from config to running
 production bundles.
 
+### When to Use the CLI
+
+The CLI is for **Bundled mode** — when you want config-as-code and separate
+deployment:
+
+| Use CLI When                | Use Integrated Mode When |
+| --------------------------- | ------------------------ |
+| Static sites, landing pages | React/Next.js apps       |
+| Docker/server deployments   | TypeScript projects      |
+| CI/CD versioned configs     | Programmatic control     |
+| Marketing/GTM workflows     | Build-time type safety   |
+
+For Integrated mode (importing directly into your app), see the
+[Collector package](../collector/).
+
 ## Installation
 
 ```bash
@@ -31,13 +46,16 @@ npm install @walkeros/cli
 walkeros bundle flow.json
 
 # Test with simulated events (no real API calls)
-walkeros simulate flow.json --event '{"name":"page view"}'
+walkeros simulate flow.json --event '{"name":"product view"}'
+
+# Or test a pre-built bundle directly
+walkeros simulate dist/bundle.mjs --event '{"name":"product view"}'
 
 # Push real events to destinations
-walkeros push flow.json --event '{"name":"page view"}'
+walkeros push flow.json --event '{"name":"product view"}'
 
 # Run a collection server locally
-walkeros run collect flow.json --port 3000
+walkeros run collect dist/bundle.mjs --port 3000
 ```
 
 ## Commands
@@ -64,7 +82,6 @@ walkeros bundle https://example.com/config.json                  # Remote URL
 - `-s, --stats` - Show bundle statistics
 - `--json` - Output stats as JSON
 - `--no-cache` - Disable package caching
-- `--local` - Run locally without Docker
 - `-v, --verbose` - Verbose output
 
 **Example:**
@@ -79,47 +96,77 @@ The output path uses convention-based defaults: `./dist/bundle.mjs` for server,
 
 ### simulate
 
-Test event processing with simulated events.
+Test event processing with simulated events. Accepts either a config JSON (which
+gets bundled) or a pre-built bundle (executed directly).
 
 ```bash
-walkeros simulate <config-file> --event '{"name":"page view"}' [options]
+walkeros simulate <input> --event '{"name":"page view"}' [options]
 ```
 
+**Input types:**
+
+- **Config JSON** - Bundled and executed with destination mocking
+- **Pre-built bundle** (`.js`/`.mjs`) - Executed directly, no mocking
+
+The CLI auto-detects the input type by attempting to parse as JSON.
+
 **Options:**
 
 - `-e, --event <json>` - Event JSON string (required)
+- `-p, --platform <platform>` - Platform override (`web` or `server`)
 - `--json` - Output results as JSON
-- `--local` - Run locally without Docker
 - `-v, --verbose` - Verbose output
 
-**Example:**
+**Examples:**
 
 ```bash
-# Simulate page view
-walkeros simulate \
-  examples/web-serve.json \
+# Simulate with config (auto-bundled)
+walkeros simulate examples/web-serve.json \
   --event '{"name":"page view","data":{"title":"Home"}}' \
   --json
+
+# Simulate with pre-built bundle
+walkeros simulate dist/bundle.mjs --event '{"name":"page view"}'
+
+# Override platform detection
+walkeros simulate dist/bundle.js --platform server --event '{"name":"page view"}'
 ```
 
+**Platform detection:**
+
+When using pre-built bundles, platform is detected from file extension:
+
+- `.mjs` → server (ESM, Node.js)
+- `.js` → web (IIFE, JSDOM)
+
+Use `--platform` to override if extension doesn't match intended runtime.
+
 ### push
 
 Execute your flow with real API calls to configured destinations. Unlike
-`simulate` which mocks API calls, `push` performs actual HTTP requests.
+`simulate` which mocks API calls, `push` performs actual HTTP requests. Accepts
+either a config JSON (which gets bundled) or a pre-built bundle.
 
 ```bash
-walkeros push <config-file> --event '<json>' [options]
+walkeros push <input> --event '<json>' [options]
 ```
 
+**Input types:**
+
+- **Config JSON** - Bundled and executed
+- **Pre-built bundle** (`.js`/`.mjs`) - Executed directly
+
+The CLI auto-detects the input type by attempting to parse as JSON.
+
 **Options:**
 
 - `-e, --event <source>` - Event to push (JSON string, file path, or URL)
   **Required**
 - `--flow <name>` - Flow name (for multi-flow configs)
+- `-p, --platform <platform>` - Platform override (`web` or `server`)
 - `--json` - Output results as JSON
 - `-v, --verbose` - Verbose output
 - `-s, --silent` - Suppress output (for CI/CD)
-- `--local` - Execute locally without Docker
 
 **Event input formats:**
 
@@ -134,6 +181,16 @@ walkeros push flow.json --event ./events/order.json
 walkeros push flow.json --event https://example.com/sample-event.json
 ```
 
+**Bundle input:**
+
+```bash
+# Push with pre-built bundle
+walkeros push dist/bundle.mjs --event '{"name":"order complete"}'
+
+# Override platform detection
+walkeros push dist/bundle.js --platform server --event '{"name":"order complete"}'
+```
+
 **Push vs Simulate:**
 
 | Feature      | `push`                              | `simulate`         |
@@ -147,8 +204,7 @@ real integrations.
 
 ### run
 
-Run flows locally using @walkeros/docker as a library (no Docker daemon
-required).
+Run flows locally (no Docker daemon required).
 
 ```bash
 walkeros run <mode> <config-file> [options]
@@ -164,7 +220,6 @@ walkeros run <mode> <config-file> [options]
 - `-p, --port <number>` - Server port
 - `-h, --host <host>` - Server host
 - `--static-dir <dir>` - Static directory (serve mode)
-- `--local` - Run locally without Docker
 - `--json` - JSON output
 - `-v, --verbose` - Verbose output
 
@@ -183,9 +238,9 @@ walkeros run serve flow.json --port 8080 --static-dir ./dist
 
 **How it works:**
 
-1. JSON configs are bundled to temp `.mjs` automatically
+1. JSON configs are auto-bundled to temp `.mjs`
 2. `.mjs` bundles are used directly
-3. Runs in current Node.js process (no containers)
+3. Runs in current Node.js process
 4. Press Ctrl+C for graceful shutdown
 
 ## Caching
@@ -444,17 +499,17 @@ Typical development cycle:
 # 1. Create/edit config
 vim my-flow.json
 
-# 2. Bundle and check stats
-walkeros bundle my-flow.json --stats
-
-# 3. Test with simulation
+# 2. Test with simulation (no real API calls)
 walkeros simulate \
   my-flow.json \
-  --event '{"name":"test event"}' \
+  --event '{"name":"product view"}' \
   --verbose
 
+# 3. Bundle and check stats
+walkeros bundle my-flow.json --stats
+
 # 4. Run locally
-walkeros run collect my-flow.json --port 3000
+walkeros run collect dist/bundle.mjs --port 3000
 
 # 5. In another terminal, test it
 curl -X POST http://localhost:3000/collect \
@@ -468,26 +523,55 @@ curl -X POST http://localhost:3000/collect \
 CLI (downloads packages + bundles with esbuild)
  ├─ Bundle → optimized .mjs file
  ├─ Simulate → test bundle with events
- └─ Run → import @walkeros/docker + execute bundle
+ └─ Run → execute bundle with built-in runtime
+```
+
+**Key principle**: CLI handles both build-time and runtime operations.
+
+## Production Deployment
+
+Deploy your flows using Docker or Node.js.
+
+### Using Docker
+
+The `walkeros/flow` image runs pre-built bundles in production:
+
+```bash
+# Build your flow
+walkeros bundle flow.json
+
+# Run with Docker
+docker run -v ./dist:/flow -p 8080:8080 walkeros/flow
 ```
 
-**Key principle**: CLI handles build-time, Docker handles runtime.
+**Custom image:**
 
-## Docker Images
+```dockerfile
+FROM walkeros/flow
+COPY dist/bundle.mjs /app/flow/
+```
+
+**Environment variables:**
 
-By default, CLI uses **explicit version tags** (not `:latest`):
+- `MODE` - `collect` or `serve` (default: `collect`)
+- `PORT` - Server port (default: `8080`)
+- `BUNDLE` - Bundle path (default: `/app/flow/bundle.mjs`)
 
-- `walkeros/cli:0.3.5` - Build tools (bundle, simulate)
-- `walkeros/docker:0.1.4` - Production runtime
+### Using Node.js
 
-Override with environment variables:
+Run the bundle directly with the CLI:
 
 ```bash
-export WALKEROS_CLI_DOCKER_IMAGE=walkeros/cli:0.3.4
-export WALKEROS_RUNTIME_DOCKER_IMAGE=walkeros/docker:latest
-walkeros bundle config.json
+# Build your flow
+walkeros bundle flow.json
+
+# Run in production
+walkeros run collect dist/bundle.mjs --port 8080
 ```
 
+This runs the flow in the current Node.js process, suitable for deployment on
+platforms like AWS Lambda, Google Cloud Run, or any Node.js hosting.
+
 ## Requirements
 
 - **Node.js**: 18+ or 22+
@@ -499,9 +583,11 @@ See [src/types.ts](./src/types.ts) for TypeScript interfaces.
 
 ## Related
 
-- [Website Documentation](https://www.walkeros.io/docs/cli/)
+- [Website Documentation](https://www.walkeros.io/docs/apps/cli/)
 - [Flow Configuration](https://www.walkeros.io/docs/getting-started/flow/)
-- [Docker Package](../docker/) - Production runtime
+- [Collector Package](../collector/) - For Integrated mode (direct imports)
+- [Operating Modes](https://www.walkeros.io/docs/getting-started/modes/) -
+  Choosing between Integrated and Bundled
 
 ## License
 

package/dist/examples/flow-order-complete.json

@@ -56,7 +56,6 @@
         }
       },
       "collector": {
-        "run": true,
         "globals": {
           "environment": "production",
           "version": "1.0.0"

package/dist/examples/flow-simple.json

@@ -22,9 +22,6 @@
             }
           }
         }
-      },
-      "collector": {
-        "run": true
       }
     }
   }

package/dist/examples/flow.json

@@ -71,7 +71,6 @@
         }
       },
       "collector": {
-        "run": true,
         "globals": {
           "environment": "production",
           "version": "1.0.0"

package/dist/index.d.ts

@@ -150,11 +150,6 @@ interface MinifyOptions {
  * Global options available across all CLI commands
  */
 interface GlobalOptions {
-    /**
-     * Execute using local Node.js environment (vs Docker container)
-     * @default false (Docker mode)
-     */
-    local?: boolean;
     /**
      * Show detailed execution logs
      * @default false
@@ -182,13 +177,17 @@ interface BundleStats {
     treeshakingEffective: boolean;
 }
 
-interface BundleCommandOptions extends GlobalOptions {
+interface BundleCommandOptions {
     config: string;
     flow?: string;
     all?: boolean;
     stats?: boolean;
     json?: boolean;
     cache?: boolean;
+    verbose?: boolean;
+    dryRun?: boolean;
+    silent?: boolean;
+    dockerfile?: boolean;
 }
 declare function bundleCommand(options: BundleCommandOptions): Promise<void>;
 /**
@@ -245,10 +244,14 @@ interface ApiCall {
     timestamp: number;
 }
 
-interface SimulateCommandOptions extends GlobalOptions {
+interface SimulateCommandOptions {
     config: string;
     event?: string;
     json?: boolean;
+    verbose?: boolean;
+    dryRun?: boolean;
+    silent?: boolean;
+    platform?: 'web' | 'server';
 }
 interface SimulationResult {
     success: boolean;
@@ -307,11 +310,14 @@ declare function simulate(configOrPath: string | unknown, event: unknown, option
 /**
  * Push command options
  */
-interface PushCommandOptions extends GlobalOptions {
+interface PushCommandOptions {
     config: string;
     event: string;
     flow?: string;
     json?: boolean;
+    verbose?: boolean;
+    silent?: boolean;
+    platform?: 'web' | 'server';
 }
 
 /**
@@ -322,9 +328,8 @@ declare function pushCommand(options: PushCommandOptions): Promise<void>;
 /**
  * Run Command Types
  *
- * Types for running walkerOS flows via CLI using @walkeros/docker as a library
+ * Types for running walkerOS flows via CLI using local runtime
  */
-
 /**
  * Run mode - determines which execution mode to use
  */
@@ -332,7 +337,7 @@ type RunMode = 'collect' | 'serve';
 /**
  * CLI command options for `walkeros run`
  */
-interface RunCommandOptions extends GlobalOptions {
+interface RunCommandOptions {
     /** Flow configuration file path (.json or pre-built .mjs) */
     config: string;
     /** Server port (overrides flow config) */
@@ -345,6 +350,12 @@ interface RunCommandOptions extends GlobalOptions {
     serveName?: string;
     /** Enable JSON output */
     json?: boolean;
+    /** Verbose logging */
+    verbose?: boolean;
+    /** Dry-run mode */
+    dryRun?: boolean;
+    /** Suppress output */
+    silent?: boolean;
 }
 /**
  * Programmatic run options (subset of CLI options)
@@ -382,8 +393,7 @@ interface RunResult {
 /**
  * Run Command
  *
- * Runs walkerOS flows using @walkeros/docker as a library
- * No Docker daemon required - runs directly in Node.js
+ * Runs walkerOS flows using local runtime
  */
 
 /**