voidzero-dev / voidzero-dev/vite-task
Investigate vp lint failure when run through vite-task
Open
@wan9chi is already working on this.
Since Jun 29, 2026.
bug
- Dominant language
- Rust
- Stars
- 466
- Forks
- 42
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 19
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.