🐛 BUG: no environment found in configuration

[cazcik]

Which Cloudflare product(s) does this pertain to?

Wrangler

What versions are you using?

4.5.0

What operating system and version are you using?

macOS Sequoia 15.3.1

Please provide a link to a minimal reproduction

No response

Describe the Bug

wrangler deploy is having trouble when passing --env stating the env does not exist even though it is described in wrangler.jsonc.

the deploy still completes however since it was unable to find the specified environment it does not get pushed with the corresponding environment's config.

wrangler.jsonc

{
  "$schema": "./node_modules/wrangler/config-schema.json",
  "name": "myapp",
  "main": "./workers/app.ts",
  "compatibility_date": "2025-03-26",
  "compatibility_flags": ["nodejs_compat"],
  "upload_source_maps": true,
  "assets": {
    "directory": "./build/client",
  },
  "observability": {
    "enabled": true,
  },
  "env": {
    "development": {
      "vars": {
        "ENVIRONMENT": "development",
      },
    },
    "production": {
      "vars": {
        "ENVIRONMENT": "production",
      },
    },
  },
}

deploy command

pnpm wrangler deploy --env development

wrangler output

 ⛅️ wrangler 4.5.0
------------------

Using redirected Wrangler configuration.
 - Configuration being used: "build/server/wrangler.json"
 - Original user's configuration: "wrangler.jsonc"
 - Deploy configuration file: ".wrangler/deploy/config.json"
▲ [WARNING] Processing build/server/wrangler.json configuration:

    - No environment found in configuration with name "development".
      Before using `--env=development` there should be an equivalent environment section in the
  configuration.
  
      Consider adding an environment configuration section to the wrangler.json file:
      ```
      [env.development]
      ```
  


Attaching additional modules:
┌─────────────────────────────────┬──────┬─────────────┐
│ Name                            │ Type │ Size        │
├─────────────────────────────────┼──────┼─────────────┤
│ assets/app-DcVQ_KQR.js          │ esm  │ 284.51 KiB  │
├─────────────────────────────────┼──────┼─────────────┤
│ assets/server-build-6hK1RppR.js │ esm  │ 1080.95 KiB │
├─────────────────────────────────┼──────┼─────────────┤
│ Total (2 modules)               │      │ 1365.45 KiB │
└─────────────────────────────────┴──────┴─────────────┘
🌀 Building list of assets...
🌀 Starting asset upload...
🌀 Found 8 new or modified static assets to upload. Proceeding with upload...
+ /.gitkeep
+ /assets/manifest-0a33de6d.js
+ /assets/chunk-GNGMS2XR-eXYBZ-pF.js
+ /assets/home-Car_vtk_.js
+ /assets/root-wo9MWzK3.js
+ /assets/entry.client-FMuzxyuH.js
+ /assets/with-props-DeHwp1uX.js
+ /assets/root-B1ryitOf.css
Uploaded 2 of 8 assets
Uploaded 5 of 8 assets
Uploaded 8 of 8 assets
✨ Success! Uploaded 8 files (1.51 sec)

Total Upload: 1365.57 KiB / gzip: 266.50 KiB
Worker Startup Time: 11 ms
No bindings found.
Uploaded myapp-development (7.10 sec)
Deployed myapp-development triggers (0.70 sec)
  https://myapp.myworker.workers.dev
Current Version ID: a7a3741e-e96e-4238-9155-62e8d95bfc84

Please provide any relevant error logs

No response

[cazcik]

this may be because i am using @react-router/dev version 7.4.0 which still has a peer dependency for wrangler@^3.28.2.

my suspicion is wrangler@^3.28.2 does not support the new wrangler config and it seems to be the case judging from the built wrangler.json in build/server/wrangler.json.

{
  "configPath": "/Users/myname/code/myapp/wrangler.jsonc",
  "userConfigPath": "/Users/myname/code/myapp/wrangler.jsonc",
  "topLevelName": "myapp",
  "legacy_env": true,
  "compatibility_date": "2025-03-26",
  "compatibility_flags": ["nodejs_compat"],
  "jsx_factory": "React.createElement",
  "jsx_fragment": "React.Fragment",
  "rules": [{ "type": "ESModule", "globs": ["**/*.js", "**/*.mjs"] }],
  "name": "domi",
  "main": "index.js",
  "triggers": { "crons": [] },
  "assets": { "directory": "../client" },
  "preview_urls": true,
  "vars": {},
  "durable_objects": { "bindings": [] },
  "workflows": [],
  "migrations": [],
  "kv_namespaces": [],
  "cloudchamber": {},
  "send_email": [],
  "queues": { "producers": [], "consumers": [] },
  "r2_buckets": [],
  "d1_databases": [],
  "vectorize": [],
  "hyperdrive": [],
  "services": [],
  "analytics_engine_datasets": [],
  "dispatch_namespaces": [],
  "mtls_certificates": [],
  "pipelines": [],
  "logfwdr": { "bindings": [] },
  "observability": { "enabled": true },
  "dev": {
    "ip": "localhost",
    "local_protocol": "http",
    "upstream_protocol": "http"
  },
  "no_bundle": true
}

seems like a fix was just merged so hopefully the next release will include it and fix this? i have yet to test with a wrangler.toml file however.

[jamesopstad]

When using the Cloudflare Vite plugin, the environment is selected at dev and build time rather than when running wrangler deploy. The current documentation for this is here - https://github.com/cloudflare/workers-sdk/tree/main/packages/vite-plugin-cloudflare#cloudflare-environments - but we're working on moving this to the docs site and making it a lot clearer. We also have a PR to improve the messaging about this if you try to run wrangler deploy --env in a project using the Vite plugin. Apologies for the confusion.

[cazcik]

using CLOUDFLARE_ENV=development pnpm run build and then CLOUDFLARE_ENV=development pnpm wrangler deploy worked like a charm for me.

thank you for the response and clarification! much appreciated. i'll close this out now.