Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
  • 哪里不对？
#445 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 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:

  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.

主要语言
TypeScript
星标
402
派生
32
平均合并
11 小时 52 分钟
30 天内合并 PR
88

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

voidzero-dev/void 的其他 Issue

查看 voidzero-dev/void 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。