Proposal: framework-aware application commands
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 28/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- nuxt, rust, typescript
- 领域
- backend-api-design, cli, tooling
调研方向
Start with the vp dev, vp build, and vp preview command-routing entry points and the package-level configuration API used by vite.config.ts. Trace how project-level .bin binaries are currently discovered by vp exec, then define how a framework adapter supplies and receives command arguments. Done means framework commands such as nuxt dev run transparently, including help and passed arguments, while framework configuration remains owned by its own config.
由索引模型根据 Issue 内容生成。
描述
Today's vp dev, vp build and vp preview are hard-written to run Vite+'s own vite, vite build, and vite preview. Users of meta frameworks like Nuxt have to use nuxt cli to start a dev server.
I propose introducing a framework-aware application commands, configured through a package-level framework API in vite.config.ts:
defineConfig({
framework: nuxt(),
fmt: { semi: false },
/* ... */
})
Inside, nuxt(), it returns the correct command that vp dev should run, like nuxt dev. It would find binaries under project-level .bin, similar to vp exec.
| Vite+ command | Framework command |
|---|---|
| vp dev | nuxt dev |
| vp build | nuxt build |
| vp preview | nuxt preview |
This means Vite+ passes all arguments to the underlying commands themselves. The usage of vp dev would be the same as nuxt dev, vp dev --help also has the same output as nuxt --help.
Framework-specific configuration would remain in the framework‘s own config file. For example, nuxt.config.ts#vite would still be the source of truth for nuxt features. Vite+ would not automatically merge them from vite.config.ts, we may even consider printing warnings for this case.
Alternative: Why not swtich modes by reading nuxt.config.ts automatically
What we hope to do is not simply nuxt support. There are hundreds of active meta frameworks on the market. Relying entirely on Vite+ to handle the logic would be extremely centralized and difficult to maintain. (Even if doing so could reduce the likelihood of AI agents making mistakes)
Why does this matter, and why is this different from raw vite
In my opinion, Vite+ is the entry point of all development process, vp lint, vp check etc. For Nuxt users, vite cli is almost Invisible, because they have their own oxlint cli and may completely skip vite cli command. When developers and agents are already familiar with vp workflow, changing to nuxt or other cli is a significant change in habits.
- 主要语言
- Rust
- 星标
- 6.3k
- 派生
- 283
- 平均合并
- 1 天 14 小时
- 30 天内合并 PR
- 208
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
voidzero-dev/vite-plus 的其他 Issue
-
`vp migrate --full` asks to set up pre-commit hooks even when they're already configured可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭contribution welcome
难度 2/5 1-3 小时 新手友好度 74/100
voidzero-dev/vite-plus#3096 · 1 条评论 · 3 个 reaction ·
维护者通常 1 天内回复
-
pending triage
难度 2/5 1-3 小时 新手友好度 72/100
voidzero-dev/vite-plus#2882 · 2 条评论 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 62/100
voidzero-dev/vite-plus#2097 · 10 条评论 · 2 个 reaction ·
维护者通常 1 天内回复
-
pending triage
难度 3/5 半天 新手友好度 78/100
voidzero-dev/vite-plus#3110 ·
维护者通常 1 天内回复
-
Exec in place instead of spawning and waiting in the CLI's wrapper processes可能已有人在做 @fengmk2 于 1 天前认领。 未关闭
voidzero-dev/vite-plus#3106 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 voidzero-dev/vite-plus 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 64/100
维护者通常 3 天内回复
-
[BUG] Filename sequence expansion (`+`) panics on numeric values exceeding `i32::MAX`可能已有人在做 @muntasir-396 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
CCExtractor/ccextractor#2402 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 70/100