You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`flare-edge-cli` scaffolds, validates, builds, deploys, tails, and tears down Go-for-Wasm Cloudflare Workers projects. It generates the Worker shim and Wrangler config, runs compatibility checks against a Workers/Wasm profile, and delegates Cloudflare operations to Wrangler and Cloudflare APIs where appropriate.
6
+
`flare-edge-cli` scaffolds, validates, builds, deploys, tails, and tears down Cloudflare Workers projects. It supports both Go-for-Wasm Workers and native JavaScript module Workers, generates Wrangler config, runs Go compatibility checks where appropriate, and delegates Cloudflare operations to Wrangler and Cloudflare APIs where appropriate.
7
7
8
-
This CLI is designed first for AI agents. Humans can use it directly, but the primary goal is to give coding agents a stable, scriptable control surface for creating and operating Cloudflare edge functions and lightweight microservices in Go.
8
+
This CLI is designed first for AI agents. Humans can use it directly, but the primary goal is to give coding agents a stable, scriptable control surface for creating and operating Cloudflare edge functions and lightweight microservices in Go or native JavaScript.
9
9
10
10
## Why This Tool Exists
11
11
12
-
`flare-edge-cli` exists to standardize the end-to-end agent workflow for Go on Cloudflare:
12
+
`flare-edge-cli` exists to standardize the end-to-end agent workflow for Cloudflare Workers:
13
13
14
14
- scaffold a deployable project with deterministic structure
15
15
- validate whether the Go code fits Workers/Wasm constraints
16
-
- build the `.wasm` artifact and Worker shim correctly every time
16
+
- build the `.wasm` artifact and Worker shim correctly for Go projects
17
+
- stage native JavaScript Worker entrypoints without changing the deploy flow
17
18
- provision and manage Cloudflare resources through one consistent interface
18
19
- emit machine-readable output that agents can inspect and chain into later actions
19
20
- tear down remote and local side effects when an ephemeral environment is no longer needed
@@ -29,7 +30,7 @@ The intended operator is usually an AI agent acting on behalf of a developer. Be
29
30
30
31
## Primary Use Case
31
32
32
-
The primary use case is simple: an AI agent needs a standard way to create and deploy an edge function or small microservice on Cloudflare using Go without rebuilding the same scaffolding, compatibility analysis, build orchestration, deployment logic, and cleanup flow for every task.
33
+
The primary use case is simple: an AI agent needs a standard way to create and deploy an edge function or small microservice on Cloudflare without rebuilding the same scaffolding, compatibility analysis, build orchestration, deployment logic, and cleanup flow for every task.
33
34
34
35
This means `flare-edge-cli` is not just a deploy wrapper. It is an agent-oriented execution surface for:
35
36
@@ -43,9 +44,10 @@ This means `flare-edge-cli` is not just a deploy wrapper. It is an agent-oriente
43
44
44
45
## What It Does
45
46
46
-
- Scaffolds Go Worker projects with a reproducible layout
47
+
- Scaffolds Go/Wasm and native JavaScript Worker projects with a reproducible layout
47
48
- Validates Go code against a Workers/Wasm compatibility profile
48
-
- Builds `.wasm` artifacts and the JavaScript Worker shim
49
+
- Builds `.wasm` artifacts and the JavaScript Worker shim for Go projects
50
+
- Stages native JavaScript Worker entrypoints for deploy, route, and doctor workflows
49
51
- Runs local or remote dev sessions through Wrangler
50
52
- Configures Workers AI bindings for Go-based AI Workers
51
53
- Deploys versioned Workers and manages routes, secrets, KV, D1, R2, and releases
@@ -65,10 +67,11 @@ The implementation is intentionally biased toward agent use:
65
67
66
68
## Requirements
67
69
68
-
- Go `1.26.0`
70
+
- Go `1.26.0` for Go/Wasm projects
69
71
-[Wrangler](https://developers.cloudflare.com/workers/wrangler/) installed and available on `PATH`
70
72
- Cloudflare authentication already configured through Wrangler or an API token
71
73
- Optional: TinyGo for `--tinygo` builds
74
+
- Optional: Cloudflare `nodejs_compat` compatibility flag for JavaScript Workers via `project init --node-compat`
72
75
73
76
## Install
74
77
@@ -123,12 +126,18 @@ go run ./cmd/flare-edge-cli --help
Diagnostics include structured fields such as rule ID, severity, file, line, message, why, and fix hint.
340
+
Diagnostics include structured fields such as rule ID, severity, file, line, message, why, and fix hint. JavaScript Worker projects skip Go static analysis and return an empty result.
312
341
313
342
### `build`
314
343
315
-
Compile Go to Wasm and inspect artifacts.
344
+
Build Go/Wasm projects or stage JavaScript Workers for deploy.
For JavaScript projects, `build` validates that the configured Worker entrypoint exists and returns it without compiling. `build wasm` remains the explicit Go-only subcommand.
359
+
329
360
### `dev`
330
361
331
362
Start a Wrangler-powered development session.
@@ -338,16 +369,17 @@ Flags `--open` and `--watch` exist as reserved compatibility flags.
0 commit comments