☂️ Plan for 2026 Q4
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- github, javascript, node.js, rust, typescript, vite
- 领域
- build-system, cli, tooling
调研方向
This issue is a Q4 roadmap covering cache behavior, remote caching, TypeScript execution, Homebrew releases, versioning, JavaScript APIs, configuration performance, Varlock, monorepo publishing, Linux file tracking, backlog triage, and Node.js support. Start by finding a specific task issue linked from the relevant section, such as #2806, #2698, #1643, or #777; the plan itself does not identify files or tests. Done depends on the chosen task and needs a narrower scope.
由索引模型根据 Issue 内容生成。
描述
The purpose of this plan is to provide transparency to our community and collaborators by sharing our current goals and timelines.
We will be actively working on the tasks listed below, which have been aligned with our goals for Q4 (Oct - Dec 2026).
If you see something that is not on this list but is strongly needed, please write a detailed requirement on this issue if you feel the need for feature prioritization. Also, remember this is not a complete list, so please search for relevant issues beforehand.
For broader collaboration, you can also find us on Discord.
P0: Cache Tools That Maintain Their Own Cache (@wan9chi)
Tools such as Vitest, TypeScript, and Astro read and rewrite their own cache files. Vite Task currently refuses to cache these tasks because their reads and writes overlap.
Support these patterns without requiring manual exclusions in cache.input or cache.output.
P0: Release Vite Task Remote Caching (@wan9chi)
Vite Task can cache task results without requiring users to define inputs manually. We intend it to replace Turborepo and Nx.
Test remote caching in real projects to prepare it for production. Release it publicly with a Workers-based service implementation.
P0: Run TypeScript with vpx (@fengmk2)
Make vpx index.ts work like tsx, so developers can run TypeScript scripts as part of their Vite+ workflow.
P0: Maintain an Official Homebrew Tap (@fengmk2)
Provide an official Homebrew tap for installing and upgrading Vite+. Connect the tap to the release process to keep it current.
P0: Align the Core Version with Vite (@fengmk2)
Increase the major version of @voidzero-dev/vite-plus-core to 8. Define how future versions map to bundled Vite versions.
With package aliases, compatible dependencies should pass peer dependency checks, while incompatible dependencies should still fail. This should reduce reliance on broad peerDependencyRules exceptions. See #2806.
P1: Define the Vite+ JavaScript API (@fengmk2, @wan9chi)
Design JavaScript APIs for Vite+ features beyond linting and formatting. These APIs should let developers use those features from scripts and integrations.
The initial scope remains open. First, decide which features and workflows to support. Include usage examples for the selected APIs.
For linting and formatting, keep the Oxlint and Oxfmt APIs unchanged. Change only the import paths to vite-plus/lint and vite-plus/fmt, respectively.
P1: Improve CLI Configuration Loading Performance (@fengmk2)
Reduce repeated loading of vite.config.ts to make vp check and vp staged faster. Establish performance baselines to measure the improvement. See #2698.
P1: Add Varlock Support (@fengmk2)
Define the initial scope and integration approach for Varlock. Then implement and document the feature.
P1: Support Monorepo Package Publishing (@fengmk2)
Support publishing multiple npm packages from a monorepo, including version management, internal dependency updates, and publishing order.
P1: Improve Automatic File Tracking on Linux (@wan9chi)
With remote caching, we expect more tasks to run on Linux CI. The current Linux backend fails on WSL2 and misses file reads made through direct syscalls. See vite-plus#1643 and vite-task#777.
Build a new Linux tracking backend that addresses these limitations.
P2: Address the Issue Backlog (@fengmk2)
Triage the issue backlog and remove duplicates. Prioritize problems that affect installation, migration, and daily use.
Reserve time throughout Q4 for issues that block users.
P2: Manage Older Node.js Versions (@fengmk2)
Support older releases such as Node.js 16, 18, and 20 in the version manager. Clarify the runtime requirements for user projects and for Vite+ itself.
- 主要语言
- Rust
- 星标
- 6.5k
- 派生
- 296
- 平均合并
- 1 天 2 小时
- 30 天内合并 PR
- 230
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
voidzero-dev/vite-plus 的其他 Issue
-
pending triage
难度 2/5 1-3 小时 新手友好度 63/100
voidzero-dev/vite-plus#3235 ·
维护者通常 1 天内回复
-
Docker guide: the runtime stage needs libatomic1 for Node.js 25 and later可能已有人在做 @kshanxs 于 5 天前认领。 未关闭documentation
难度 2/5 1-3 小时 新手友好度 84/100
voidzero-dev/vite-plus#3219 · 2 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
pending triage
难度 2/5 1-3 小时 新手友好度 72/100
voidzero-dev/vite-plus#2882 · 2 条评论 ·
维护者通常 1 天内回复
-
`vp create` doesn't rewrite `vite` imports when adding a third-party template to a monorepo可能已有人在做 @voidzero-bot 今天认领。 未关闭- P2: has workaround pending triage triage: fix verified
难度 3/5 1-2 天 新手友好度 35/100
voidzero-dev/vite-plus#3281 · 1 条评论 ·
维护者通常 1 天内回复
-
`npm install -g` keeps the `bin` link on the old version after the default Node.js changes可能已有人在做 @mondaychen 今天认领。 未关闭bug triage: failed
voidzero-dev/vite-plus#3279 · 1 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 voidzero-dev/vite-plus 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
compiler P4 perf
难度 2/5 1-3 小时 新手友好度 78/100
HerringtonDarkholme/hd-lang#1044 ·
维护者通常 1 天内回复
-
good first issue help wanted r-docs
难度 2/5 1-3 小时 新手友好度 72/100
servo/rust-smallvec#824 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 90/100
akitaonrails/ai-usagebar#552 ·
维护者通常 1 天内回复