Expose build mode support from autoconfig

[edmundhung]

Fixes cloudflare/cf#180.

Autoconfig resolves the framework commands used by cf build and cf dev, but callers could not tell which commands consume Cloudflare build modes or execute them without reparsing a display string. This adds spawn-ready, command-scoped metadata to autoconfig details and summaries:

commands: {
  build?: {
    executable: string;
    args: string[];
    supportsMode: boolean;
  };
  dev?: {
    executable: string;
    args: string[];
    supportsMode: boolean;
  };
}

Frameworks opt each command into mode forwarding individually. Astro and Vite build and development commands report supportsMode: true; unsupported commands default to false. This keeps Angular ng build unchanged and correctly marks it unsupported even when Wrangler is the configured Cloudflare build tool.

Detected command strings are parsed once into an executable and argument vector. Quoted values remain single arguments, while shell control operators are rejected because they cannot be represented by a direct subprocess spawn.

buildTool?: "vite" | "wrangler" remains available to identify the Cloudflare-aware tool configured by autoconfig. It is deliberately separate from the capabilities of the framework command being executed. Existing buildCommand, deployCommand, and versionCommand string fields are preserved for current output consumers.

The corresponding cf change can append --mode to supported framework invocations and execute both framework and Cloudflare delegates through the shared structured subprocess runner, replacing execaCommand without string concatenation.

---

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
  • Additional testing not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: this exposes integration metadata consumed by cf and does not add a direct user-facing API workflow.

Verification:

• pnpm test:ci in packages/autoconfig (208 tests)
• pnpm check:type in packages/autoconfig
• pnpm build in packages/autoconfig
• oxlint --deny-warnings --type-aware on changed TypeScript files
• oxfmt --check on changed files

[changeset-bot]

🦋 Changeset detected

Latest commit: fa1708b

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

This PR includes changesets to release 1 package

Name	Type
@cloudflare/autoconfig	Minor

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

[ask-bonk]

LGTM

github run

[pkg-pr-new]

@cloudflare/autoconfig

npm i https://pkg.pr.new/@cloudflare/autoconfig@15593

@cloudflare/build-output-utils

npm i https://pkg.pr.new/@cloudflare/build-output-utils@15593

@cloudflare/codemods

npm i https://pkg.pr.new/@cloudflare/codemods@15593

@cloudflare/config

npm i https://pkg.pr.new/@cloudflare/config@15593

create-cloudflare

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

@cloudflare/deploy-helpers

npm i https://pkg.pr.new/@cloudflare/deploy-helpers@15593

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-functions

npm i https://pkg.pr.new/@cloudflare/pages-functions@15593

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-plugin

npm i https://pkg.pr.new/@cloudflare/vitest-plugin@15593

@cloudflare/workers-auth

npm i https://pkg.pr.new/@cloudflare/workers-auth@15593

@cloudflare/workers-editor-shared

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

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@15593

wrangler

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

commit: fa1708b