Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Allow `vp staged` to resolve workspace-root config from subdirectories

オープン
  • 何か問題がありますか？
#2,177 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
静か
技術スタック
typescript
領域
cli, tooling

調査の方向性

packages/cli/src/staged/bin.ts から始め、次に packages/cli/src/resolve-vite-config.ts にある workspace に限定されたトラバーサルと、packages/cli/src/pack-bin.ts でのその使用箇所を読みます。上記で説明されている root-config-from-package シナリオを再現し、その後、package-local な Vite config のエッジケースを含め、単一の config 解決および実行スコープのポリシーを確立して検証します。

索引モデルが issue の本文から書いたものです。

説明

pending triage
Description

In a monorepo, vp staged fails when invoked from a workspace package if the staged config exists only in the workspace-root vite.config.ts.

This is common with coding agents: after inspecting or editing one package, they often keep that package as the working directory when running validation commands.

repo/
├── package.json          # workspaces: ["packages/*"]
├── vite.config.ts        # contains staged config
└── packages/
    └── app/
        └── src/index.ts

// repo/vite.config.ts
export default {
  staged: {
    '*.{js,ts,tsx}': 'vp check --fix',
  },
}

git add packages/app/src/index.ts
cd packages/app
vp staged

Actual result:

error: No "staged" config found in vite.config.ts. Please add a staged config

A normal pre-commit hook usually hides this behavior because Git starts client-side hooks from the worktree root, regardless of where git commit was entered.

Current behavior

The following was verified with an isolated Git monorepo:

Invocation Config File/task scope
Run from repository root Root vite.config.ts Repository
Run from a package with no local staged config None; exits with an error Nothing runs
Run from a package with a local staged config Package config Package CWD
Run from a package with --cwd <workspace-root> Root config Repository
Run through a Git pre-commit hook Root config, because Git uses the worktree root Repository

Internally, Vite+ resolves one staged object from the invocation CWD and passes it through lint-staged's programmatic config option. lint-staged still resolves the Git repository and staged files, but its own multi-config discovery is bypassed.

Ecosystem patterns

Existing tools use different models:

Model Tools Behavior
Hook manager Git, Husky, simple-git-hooks Git starts hooks at the worktree root. The manager executes a literal hook command; package-specific CWD or filtering is left to that command.
Central root config pre-commit, Lefthook The tool resolves the Git root and loads a repository-level config. Package behavior is expressed through filters or per-command root settings.
Distributed config lint-staged The tool can discover multiple configs, assign each staged file to its closest config, and run tasks from the selected config directory. Configs are isolated rather than merged.
Current Vite+ behavior vp staged Git state is repository-aware through lint-staged, while Vite config lookup remains limited to the invocation CWD.

Relevant details:

Design choices

There are two separate decisions. This issue does not propose a preferred combination.

1. Where should config come from?
  • Current CWD only: preserve existing behavior; improve documentation/error output and require callers to use root CWD or --cwd.
  • Workspace/Git root: always use one central root policy.
  • Nearest ancestor config: walk upward to the workspace root. This could stop at the first Vite config, or continue until finding one that defines staged.
  • Multiple configs: discover package/root staged configs and assign files to them independently.
  • Explicit selection: add an option such as --config or --root; this can supplement any implicit rule.

Important edge case: a package may have a vite.config.ts for build settings but keep staged only at the workspace root. “Nearest Vite config” and “nearest config defining staged” produce different results.

2. What should the execution scope be?
  • Repository root: task CWD, glob base, and staged-file scope all use the root.
  • Invocation directory: an inherited/root config can be used while files and tasks remain scoped to the package from which the command was launched.
  • Config directory: tasks and file matching follow whichever config was selected.

These choices have different consequences. Root scope may process staged files in sibling packages; invocation scope may run root-defined commands from a package CWD; config-directory scope becomes more complex if multiple configs are supported.

Possible combinations include:

  • root config + root scope;
  • nearest ancestor config + invocation scope;
  • current behavior + an explicit config/root option;
  • multiple configs + per-config task scope.
Relevant implementation
Validations
  • Read the Contributing Guidelines.
  • Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
  • Checked that there is not already an open issue requesting the same behavior.
主要言語
Rust
スター
6k
フォーク
271
平均マージ
1日 12時間
マージ済み PR（30日）
198

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

voidzero-dev/vite-plus のほかの issue

voidzero-dev/vite-plus の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。