voidzero-dev / voidzero-dev/vite-task
Proposal: Dogfood Vite Task in this repository (self-host the repo tasks)
まだ誰も着手していません。
- 主要言語
- Rust
- スター
- 466
- フォーク
- 42
- 平均マージ
- 1日 15時間
- マージ済み PR(30日)
- 19
説明
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.
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
調査の方向性
この提案では現在の just の構成とリポジトリのワークフローに触れていますが、ファイルやテストは挙げられていません。まず、既存のタスクがどのように整理されているかを確認し、それをこの Rust に重点を置いたモノレポにおける Vite Task の機能と比較してください。完了とするには、合意された移行範囲と成功基準が必要ですが、issue ではそれらが定義されていません。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- rust, vite
- 領域
- build-system, tooling
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 25/100