configure C3 experimental projects to use @cloudflare/autoconfig directly - #14904
configure C3 experimental projects to use @cloudflare/autoconfig directly#14904dario-piotrowicz wants to merge 1 commit into
@cloudflare/autoconfig directly#14904Conversation
🦋 Changeset detectedLatest commit: cd34d92 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
|
✅ All changesets look good |
|
I've completed my analysis. The change is well-structured. The main behavioral observations:
These are minor/low-severity observations, not concrete bugs with a clear fix that I should provide as a suggestion. The Wrangler-install-on-configured difference is a design judgement (a fresh scaffold is never pre-configured), and I shouldn't post a speculative suggestion that changes behavior without certainty. Nothing else rises to actionable severity per the guidelines (no logic bugs, security issues, backward-compat violations, or incorrect API behavior in the actual usage path). LGTM |
@cloudflare/autoconfig
@cloudflare/config
create-cloudflare
@cloudflare/deploy-helpers
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-functions
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-auth
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
3509514 to
6b79d96
Compare
6b79d96 to
cd34d92
Compare
|
Codeowners approval required for this PR:
Show detailed file reviewers
|
C3 for frameworks in experimental mode right now spawns a
wrangler setupprocess. This is not super efficient and it also ties C3 to Wrangler which is not ideal (givencfand all).So in this PR I am updating C3 to use the autoconfig package directly instead.
A picture of a cute animal (not mandatory, but encouraged)