@astrojs/cloudflare v13 ignores --env during deploy

[mark-mybaggage]

Astro Info

Astro                    v6.0.8
Vite                     v7.3.1
Node                     v22.15.0
System                   Windows (x64)
Package Manager          npm
Output                   server
Adapter                  @astrojs/node (v10.0.3)
Integrations             @astrojs/alpinejs (v0.5.0)
                         @astrojs/sitemap (v3.7.1)

If this issue only occurs in one browser, which browser is a problem?

No response

Describe the Bug

When attempting to deploy an application to a different environment using the --env parameter does not work. This does not happen with @astrojs/cloudflare v12 and earlier. This could be related to the Wrangler configuration file now being optional.

The project contains a wrangler.jsonc file with the name property:

"name": "corp-frontend"

When testing the deploy command is:

npx wrangler deploy --env sneak

The 'sneak' value is ignored and the code is deployed to corp-frontend

What's the expected result?

The expected result is to deploy to:

corp-frontend-sneak

Link to Minimal Reproducible Example

n/a

Participation

• I am willing to submit a pull request for this issue.

[astrobot-houston]

I was able to reproduce this issue. In @astrojs/cloudflare v13, the build pipeline was fundamentally changed to use @cloudflare/vite-plugin. During the build, the plugin resolves the wrangler config into a flat, generated wrangler.json in the build output directory (e.g., dist/ssr/wrangler.json) and writes a deploy redirect config at .wrangler/deploy/config.json. This generated config does not contain env sections or a targetEnvironment marker, so when npx wrangler deploy --env sneak is run post-build, wrangler follows the redirect to the generated config and the --env parameter is effectively ignored because there are no environment-specific overrides to apply. In v12, wrangler deploy ran directly against the user's original wrangler.toml/wrangler.jsonc which contained [env.*] sections, so --env worked as expected.

I was unable to find a fix for this issue. This is a consequence of how @cloudflare/vite-plugin generates the output wrangler config — the environment-specific sections from the user's original config are not preserved in the generated output. As a workaround, you can set the CLOUDFLARE_ENV environment variable when running astro build (e.g., CLOUDFLARE_ENV=sneak astro build) so that the build resolves the correct environment's config into the output. You would need to build separately for each target environment. A proper fix would likely need to happen in the @cloudflare/vite-plugin to either preserve env sections in the generated config or set the targetEnvironment field appropriately. This should be reported upstream to the @cloudflare/vite-plugin team as well.

P3: minor bug. This affects users who deploy to multiple Cloudflare environments using --env, which is a specific but legitimate workflow. A workaround exists (CLOUDFLARE_ENV at build time), but it requires building separately per environment, which is a workflow change. The root cause is in the upstream @cloudflare/vite-plugin rather than in @astrojs/cloudflare itself.

Full Triage Report

Root Cause Analysis

Background

@astrojs/cloudflare v13 underwent a major architectural change (PR #14306, PR #15037). The adapter now uses @cloudflare/vite-plugin to handle the build pipeline, replacing the previous approach where the build output was a standalone _worker.js bundle and wrangler operated directly on the user's config file.

What Changed

v12 and earlier:

• astro build produced dist/_worker.js/index.js
• User's wrangler.toml/wrangler.jsonc pointed main to the built output
• npx wrangler deploy --env sneak read the user's original config, including [env.sneak] sections
• --env worked correctly

v13:

• astro build invokes @cloudflare/vite-plugin which:
  1. Reads the user's wrangler config (if present) and resolves it for the current environment
  2. Applies Astro's cloudflareConfigCustomizer (packages/integrations/cloudflare/src/wrangler.ts)
  3. Generates a new, flat wrangler.json in the build output (e.g., dist/ssr/wrangler.json) — this config has env-specific values already merged and does NOT contain env sections
  4. Writes .wrangler/deploy/config.json that redirects wrangler to the generated config
• When npx wrangler deploy --env sneak runs, wrangler discovers the redirect config, follows it to the generated wrangler.json, and since this is a "redirected config" with no env sections and no targetEnvironment field, the --env sneak parameter is silently ignored

Key Code Locations

• packages/integrations/cloudflare/src/index.ts:214-218 — cfVitePlugin() invocation
• packages/integrations/cloudflare/src/wrangler.ts:17-57 — cloudflareConfigCustomizer (sets defaults, does not handle env sections)
• @cloudflare/vite-plugin resolvePluginConfig — Reads CLOUDFLARE_ENV env var to determine build-time environment
• @cloudflare/vite-plugin outputConfigPlugin — Generates the flat output wrangler.json from the resolved config

Workaround

Set CLOUDFLARE_ENV=sneak when running astro build:

CLOUDFLARE_ENV=sneak astro build
npx wrangler deploy

Note: this requires a separate build per target environment and --env is no longer needed at deploy time.

Upstream Issue

The root cause is in @cloudflare/vite-plugin which strips environment sections when generating the output config. This should be reported to the Cloudflare workers-sdk repository.

This report was made by an LLM. Mistakes happen, check important info.

[github-actions]

Hello @mark-mybaggage. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with needs repro will be closed if they have no activity within 3 days.

[alexanderniebuhr]

But as you can see in the linked issue the workaround is to use the CLOUDFLARE_ENV variable. That is even the suggested way Cloudflare documents here.

[lifeforcedev]

For me the missing piece was that platformProxy.environment must read CLOUDFLARE_ENV and that value must match the [env.<name>] section in wrangler.toml. Added docs here: withastro/docs#13995