Cloudflare Workers Production Pack

The agent loads cloudflare-workers-production, then workers-wrangler-config, and runs the linter:

$ node lint-wrangler-config.mjs wrangler.jsonc
ERROR name-invalid name "orders_api" may contain only letters, digits and dashes (no underscores).
WARN  compat-date-old compatibility_date 2025-11-03 is 344 days old. Read the compatibility flags changelog, bump it, run tests and `wrangler types`.
ERROR secret-in-vars top level: var STRIPE_SECRET_KEY has a secret-like name. Move it to a secret (`wrangler secret put STRIPE_SECRET_KEY`) and .dev.vars for local dev.
ERROR custom-domain-pattern top level: custom domain "api.example.com/*" contains a wildcard. Custom Domains match one exact hostname.
ERROR custom-domain-pattern top level: custom domain "api.example.com/*" contains a path. Custom Domains take the whole hostname; use a route for path matching.
WARN  do-legacy-storage migration v1: new_classes creates a key-value backed class (RateLimiter). Use new_sqlite_classes for new classes.
WARN  env-missing-binding env.staging: vars entry STRIPE_SECRET_KEY exists at the top level but not in this environment.
WARN  env-missing-binding env.staging: "durable_objects" is set at the top level but not in this environment. Bindings and vars are not inherited; this environment deploys without them.
WARN  env-missing-binding env.staging: "d1_databases" is set at the top level but not in this environment. Bindings and vars are not inherited; this environment deploys without them.
WARN  env-inherits-routes env.staging: inherits the top-level routes (api.example.com/*). Deploying it moves those routes and custom domains to the environment's Worker. Give it its own routes or "routes": [].
INFO  observability-unset observability is not set. New Workers default to logs on, but set "observability": { "enabled": true } so the config stays the source of truth.
INFO  secrets-undeclared No secrets.required list. Declare secret names so `wrangler deploy` fails when one is missing and `wrangler types` types them without .dev.vars.
WARN  types-missing No generated types file (worker-configuration.d.ts). Run `wrangler types` and commit the output; run `wrangler types --check` in CI.
4 error(s), 7 warning(s), 2 note(s)

It explains the 500s: d1_databases and durable_objects are not inherited by env.staging, so the staging Worker has no DB. It flags two problems that would have hit production next: staging inherits routes, so wrangler deploy --env staging would move api.example.com to the staging Worker, and new_classes would create the rate limiter on the key-value backend, which can never be converted to SQLite. Since nothing is deployed yet, it declares the class in exports with SQLite storage, moves the Stripe key to a secret, and gives staging its own bindings and domain:

{
  "$schema": "./node_modules/wrangler/config-schema.json",
  "name": "orders-api",
  "main": "src/index.ts",
  "compatibility_date": "2026-10-01",
  "workers_dev": false,
  "preview_urls": false,
  "observability": { "enabled": true, "head_sampling_rate": 1 },
  "routes": [{ "pattern": "api.example.com", "custom_domain": true }],
  "exports": {
    "RateLimiter": { "type": "durable-object", "storage": "sqlite" }
  },
  "secrets": { "required": ["STRIPE_SECRET_KEY"] },
  "vars": { "ENVIRONMENT": "production" },
  "d1_databases": [
    { "binding": "DB", "database_name": "orders", "database_id": "<PRODUCTION_D1_ID>" }
  ],
  "durable_objects": {
    "bindings": [{ "name": "RATE_LIMITER", "class_name": "RateLimiter" }]
  },
  "env": {
    "staging": {
      "routes": [{ "pattern": "staging-api.example.com", "custom_domain": true }],
      "secrets": { "required": ["STRIPE_SECRET_KEY"] },
      "vars": { "ENVIRONMENT": "staging" },
      "d1_databases": [
        { "binding": "DB", "database_name": "orders-staging", "database_id": "<STAGING_D1_ID>" }
      ],
      "durable_objects": {
        "bindings": [{ "name": "RATE_LIMITER", "class_name": "RateLimiter" }]
      }
    }
  }
}

It sets the secret per environment with npx wrangler secret put STRIPE_SECRET_KEY --env staging, puts the local value in .dev.vars, runs npx wrangler types (which now types STRIPE_SECRET_KEY: string and ENVIRONMENT: "staging" | "production"), and reruns the checks:

$ node lint-wrangler-config.mjs wrangler.jsonc
0 error(s), 0 warning(s), 0 note(s)

$ npx wrangler deploy --dry-run --env staging
Total Upload: 0.45 KiB / gzip: 0.29 KiB
Your Worker has access to the following bindings:
Binding                                Resource
env.RATE_LIMITER (RateLimiter)         Durable Object
env.DB (orders-staging)                D1 Database
env.ENVIRONMENT ("staging")            Environment Variable
--dry-run: exiting now.

Both configs, the linter output and the dry-run output above are real runs on wrangler 4.150.0. Finally it adds wrangler types --check, the D1 migrations apply --remote step and the deploy to CI from workers-testing-release.