Fix autoconfig for Astro 6+ projects to skip wrangler config generation

[dario-piotrowicz]

Astro 6+ generates its own wrangler configuration on build, so autoconfig now detects the Astro version and skips creating a wrangler.jsonc file for projects using Astro 6 or later. This prevents conflicts between the autoconfig-generated config and Astro's built-in config generation.

---

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
  • Additional testing not necessary because: already tested in the experimental C3 e2es
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: establishes expected behavior

A picture of a cute animal (not mandatory, but encouraged)

---

[changeset-bot]

🦋 Changeset detected

Latest commit: 3af5fdf

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

✅ All changesets look good

[ask-bonk]

I'm Bonk, and I've done a quick review of your PR.

This PR makes autoconfig skip wrangler config generation for Astro 6+ projects (which generate their own wrangler config on build), by checking the installed Astro version with semiver and returning wranglerConfig: null for v6+.

Issues found:

1. Copy-paste JSDoc bug (low severity): The getAstroVersion function's JSDoc comment says Gets the installed version of the "@solidjs/start" package — it was copied from solid-start.ts without updating the description. Posted a suggestion comment to fix it.

The rest of the changes look correct — the null-handling for wranglerConfig is properly threaded through buildOperationsSummary, the dry-run path, and the actual config-writing path. The type changes in types.ts and index.ts are consistent.

github run

[pkg-pr-new]

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@12856

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@12856

miniflare

npm i https://pkg.pr.new/miniflare@12856

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@12856

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@12856

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@12856

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@12856

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@12856

wrangler

npm i https://pkg.pr.new/wrangler@12856

commit: 6a2e604

[workers-devprod]

Codeowners approval required for this PR:

• ✅ @cloudflare/wrangler

Show detailed file reviewers

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 3 additional findings.

[edmundhung]

Out of curiosity: if there is no wrangler config, how does astro decide the worker name in the generated config? based on the directory?

[ascorbic]

package.json name, then directory

[edmundhung]

@dario-piotrowicz I think you need to remove quarantine: true from the test config too.

[ascorbic]

astro add cloudflare should create a wrangler.jsonc in older versions of Astro too, so I'm not sure you need the version check

[dario-piotrowicz]

@dario-piotrowicz I think you need to remove quarantine: true from the test config too.

good call! 🫡

Done: 3af5fdf

[dario-piotrowicz]

astro add cloudflare should create a wrangler.jsonc in older versions of Astro too, so I'm not sure you need the version check

oof.... this is a problem! 😓

The astro add x logic is part of the astro package, that is why I added the version check

Unfortunately it seems like it tries to install latest versions of the packages (that's why I guess you were asking if the version check is needed). This doesn't actually work in older version of astro because of dependency incompatibilities... see:

Meaning that we can fix this for current versions of Astro but projects using older version of Astro won't be auto-configurable 😓 mh... I am not sure how we can deal with that... the only options that come to mind for me are either not supporting older Astro majors or re-implement the astro add cloudflare logic in autoconfig for older Astro versions ourselves... 😓

what do you think?

[ascorbic]

Oh weird. I assumed it would be a bit smarter there. That's not great