Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Track Cloudflare Vite plugin v2 typed config and native Build Output support

Aperta
  • Qualcosa non va?
#445 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript, vite
Ambito
build-system, devops

Direzione di ricerca

Read PR #444 and the inspected Void source revision, then trace the framework's plugin configuration, artifact preparation, preview, prerender, and publication consumers. Start at the existing configPath and dist/{ssr,rsc,server}/wrangler.json boundaries, and compare them with cloudflare.config.ts and .cloudflare/output/v0. Done means root and Worker configuration, native artifact metadata and bytes, preview/prerender, and application migration checks all satisfy the listed acceptance cases.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Cloudflare Vite plugin 2.0.0-beta.v.0 introduces typed Cloudflare configuration and native Build Output. Void 1.1.11 currently passes generated Wrangler configuration through configPath and later reads dist/{ssr,rsc,server}/wrangler.json. A dependency override alone cannot preserve these contracts.

Inspected Void source: https://github.com/voidzero-dev/void/tree/134a2ee5052458242e15273c0db6aecaa5760249
Inspected published Cloudflare package: @cloudflare/[email protected], declaring @cloudflare/[email protected].

The adapter needs to address these boundaries:

  • Root config: v2 loads cloudflare.config.ts and no longer accepts configPath. Its Worker config callback does not carry root accountId, complianceRegion or containers. A Worker-only bridge would drop root settings.
  • Worker config: the typed schema uses entrypoint, compatibilityDate, typed env and exports rather than Wrangler main, compatibility_flags, vars, d1_databases and durable_objects. Preserve authored binding IDs and precedence, required secrets, flag deduplication and Durable Object migration metadata.
  • Artifact consumption: v2 writes .cloudflare/output/v0 directly, with partial module manifests and additional module types. Preparation, publish validation, preview and prerender should consume the same immutable native artifact through the public utilities. Keep the v1 converter independently tested if v1 remains supported.
  • Metadata: preserve the original build mode and account selection, including explicit target-account mismatch validation.

Acceptance cases:

  1. An app without optional services builds and previews from native v2 output without credentials or paid bindings.
  2. A custom TanStack entry preserves default handlers and named Durable Object/Workflow exports in development and production.
  3. Bindings, secret declarations, flags, asset routing, migration history, queues and root account/container settings survive exactly once.
  4. Additional text/binary/Wasm module types, assets and build metadata survive preparation and publication of the same immutable artifact.
  5. Preview/prerender, framework artifact checks and packed-consumer checks pass across supported systems.
  6. Existing real cf --prebuilt --dry-run coverage passes without publication. Credentialed deployment tests remain a separate gate.

This is a source-level compatibility assessment. No v2 app deployment or authenticated provider operation was attempted. The inspected beta still contains CLOUDFLARE_CF_AUTH and CLOUDFLARE_AUTH_USE_KEYRING; no auth-flag rename is indicated by these sources.

Implementation progress

Native Build Output preparation is implemented in PR #444. The public converter consumes the standard v2 artifact, completes module manifests with the standard reader, preserves original metadata and module/asset bytes, and leaves the input unchanged. The final upstream test suite passed 13,554 tests; packed React consumer checks passed for npm/pnpm with plain Vite and Vite+. A real Vite plugin 2.0.0-beta.v.0 build also passed converter preparation and cf prebuilt dry-run.

This does not complete the full migration. Void's internal plugin configuration and artifact consumers still need to switch to v2. The fixed configuration-file location remains a separate framework integration prerequisite: the Worker callback alone cannot provide root account settings and Containers. This issue stays open for that configuration boundary, native preview/prerender/publication consumers, and application-level migration verification.

Lingua principale
TypeScript
Stelle
402
Fork
32
Merge medio
11h 52m
PR unite (30g)
88

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di voidzero-dev/void

Tutte le issue di voidzero-dev/void

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.