Proposal: Dogfood Vite Task in this repository (self-host the repo tasks)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
- 技术栈
- rust, vite
- 领域
- build-system, tooling
调研方向
该提案提到了当前的 just 设置和仓库工作流，但没有列出任何文件或测试。首先检查现有任务是如何组织的，并将其与 Vite Task 针对这个以 Rust 为重点的 monorepo 所具备的能力进行比较。要视为完成，必须先就迁移范围和成功标准达成一致，而该 issue 并未定义这些内容。
由索引模型根据 Issue 内容生成。
描述
First of all, sorry if this is a noisy or unnecessary suggestion.
I just wanted to share this with a lot of respect: Vite Task already feels extremely well designed, and I genuinely think it has the potential to be useful beyond the JS/TS ecosystem, including repositories with a strong Rust focus like this one.
At the moment, this repository appears to use just for task orchestration. Since Vite Task itself is a monorepo task runner, I was wondering whether it might be interesting to dogfood it here and gradually self-host the repository tasks with Vite Task itself.
I think this could have a few benefits:
- It would serve as a strong real-world example of Vite Task managing its own development workflows.
- It would demonstrate that the tool is not limited to JS/TS-heavy repositories, but can also fit mixed or Rust-centric monorepos.
- Dogfooding could help uncover UX gaps, missing features, or rough edges earlier.
- It would make the project story even stronger: the tool is good enough to run itself.
I am not suggesting this as “Just is wrong” or that migration should be rushed. just is great, and there may be perfectly good reasons to keep the current setup. I only wanted to suggest that self-hosting could be a compelling direction if it aligns with the project goals.
Even a partial migration could be interesting at first, for example:
- introducing Vite Task for a subset of repository workflows,
- comparing ergonomics/performance with the current setup,
- and expanding only if it proves valuable.
In any case, thank you for building this. It already looks like a really promising piece of tooling, and I would love to see it adopted across ecosystem boundaries, not only in JS/TS projects but also in repositories that include Rust and other languages.
- 主要语言
- Rust
- 星标
- 468
- 派生
- 42
- 平均合并
- 2 天 6 小时
- 30 天内合并 PR
- 30
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
voidzero-dev/vite-task 的其他 Issue
-
难度 5/5 一周以上 新手友好度 35/100
voidzero-dev/vite-task#738 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 78/100
voidzero-dev/vite-task#719 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
voidzero-dev/vite-task#717 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
voidzero-dev/vite-task#700 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 78/100
voidzero-dev/vite-task#699 ·
维护者通常 1 天内回复
查看 voidzero-dev/vite-task 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
trailofbits/dylint#2107 ·
维护者通常 1 天内回复
-
area:cli bug good first issue priority:medium
难度 2/5 1-3 小时 新手友好度 90/100
维护者通常 1 天内回复
-
arrays_zip with two same-named inputs fails with "ArrowArray struct has 2 children (expected 1)"未关闭bug requires-triage
难度 2/5 1-3 小时 新手友好度 78/100
apache/datafusion-comet#6251 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug false-positive harper-core linting
难度 2/5 1-3 小时 新手友好度 68/100
Automattic/harper#4471 ·
维护者通常 1 天内回复