voidzero-dev / voidzero-dev/vite-task
Investigate vp lint failure when run through vite-task
Offen
@wan9chi arbeitet bereits daran.
Seit 29.6.2026.
bug
- Vorherrschende Sprache
- Rust
- Sterne
- 466
- Forks
- 42
- Ø Merge
- 1 T. 15 Std.
- Gemergte PRs (30 T.)
- 19
Beschreibung
Follow-up from https://github.com/voidzero-dev/vite-plus/pull/1944#issuecomment-4800894266
There appears to be an exception related to vite-task: vp lint runs normally when executed directly, but fails after passing through the task runner.
Repro:
docker run --rm ghcr.io/voidzero-dev/vite-plus:pr-1944 bash -c \
'vp create vite:monorepo --directory hello --no-interactive && cd hello && vp lint && vp run ready'\n```\n\nObserved failure:\n- direct `vp lint` succeeds\n- `vp run ready` fails while running `vp check` / `tsgolint`\n- error includes: `spawnSync .../tsgolint EINVAL`\n\nRelevant excerpt:\n```\nError running tsgolint: "exit status: exit status: 1"\nError: spawnSync /app/hello/node_modules/.pnpm/@oxlint-tsgolint+linux-x64@0.23.0/node_modules/@oxlint-tsgolint/linux-x64/tsgolint EINVAL\n```\n\nContext from the original report:\n- Node 24.18.0\n- pnpm 11.9.0\n- generated via `vp create vite:monorepo`\n\nLikely next step:\n- compare environment/process spawning differences between direct invocation and vite-task runner execution\n- verify whether stdio/env/cwd handling is causing `tsgolint` spawn failure
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.