Track Cloudflare Vite plugin v2 typed config and native Build Output support
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 25/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- typescript, vite
- 領域
- build-system, devops
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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:
- An app without optional services builds and previews from native v2 output without credentials or paid bindings.
- A custom TanStack entry preserves default handlers and named Durable Object/Workflow exports in development and production.
- Bindings, secret declarations, flags, asset routing, migration history, queues and root account/container settings survive exactly once.
- Additional text/binary/Wasm module types, assets and build metadata survive preparation and publication of the same immutable artifact.
- Preview/prerender, framework artifact checks and packed-consumer checks pass across supported systems.
- 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.
- 主要語言
- TypeScript
- 星號
- 402
- 分支
- 32
- 平均合併
- 12 小時 1 分鐘
- 30 天內合併 PR
- 80
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
voidzero-dev/void 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 78/100
voidzero-dev/void#484 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
voidzero-dev/void#463 ·
維護者通常 1 天內回覆
-
Deploy after a secret change fails for Workers over ~750 KB: source read-back capped at 1 MiB可能已有人在做 @Brooooooklyn 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 82/100
voidzero-dev/void#459 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
bug
難度 1/5 1-3 小時 新手友好度 78/100
voidzero-dev/void#428 ·
維護者通常 1 天內回覆
-
Allow `npm create void` and `void init` to run without prompts可能已有人在做 @ashunar0 今天認領。 未關閉
難度 4/5 3-5 天 新手友好度 57/100
voidzero-dev/void#491 · 1 則留言 ·
維護者通常 1 天內回覆
查看 voidzero-dev/void 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 78/100
jessepollak/home#2223 ·
維護者通常 1 天內回覆
-
grep fixture corpus test follows the corpus's loop symlink under the receipt runner (fails on main)未關閉
難度 2/5 1-3 小時 新手友好度 68/100
code-yeongyu/senpi#3756 ·
維護者通常 1 天內回覆
-
org:external package:deepagents priority:triage topic:memory topic:middleware type:bug
難度 2/5 1-3 小時 新手友好度 65/100
langchain-ai/deepagents#7059 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 92/100
osmlab/name-suggestion-index#12992 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 66/100
hemilabs/ui-monorepo#2506 ·
維護者通常 1 天內回覆