feat: integrate vite-task runner-aware tools (auto output + tracked envs) by wan9chi · Pull Request #1774 · voidzero-dev/vite-plus

wan9chi · 2026-06-06T17:08:30Z

Integrates the runner-aware-tools work now available on vite-task/main: Vite reports its inputs/outputs/envs to the vp runner via @voidzero-dev/vite-task-client, so vp build no longer needs a hand-synthesized cache config. This enables auto output restoration and auto tracked envs through the runner protocol.

Changes

Bump vite-task git deps to 82ec12b2 (latest main): runner-aware IPC server/client + embedded napi addon, tracked env fingerprinting, automatic output tracking/restoration by default, per-schema-version cache directories, and prefix-env executable lookup fixes. Regenerate the napi binding (RunnerClient/load exports) and run-config.ts for the new task-config types (AutoTracking).
Point the vite behind vp build/vp dev to latest vitejs/vite (c13a37b53), which carries the vite-task-client integration. vite lists @voidzero-dev/vite-task-client in devDependencies, so it is bundled into vite's output, and therefore into @voidzero-dev/vite-plus-core, the same way as vite's other bundled deps (cac, esbuild, ...). No extra runtime dependency or build wiring is needed.
Remove vp build's synthetic cache config (env: ["VITE_*"], manual input excludes). The all-None EnabledCacheConfig keeps caching enabled with auto input/output inference; vite's ignoreInput/ignoreOutput/getEnv/getEnvs refine the fingerprint at runtime. vp dev stays disabled().
Docs: update cache/run docs for automatic output restoration by default and output: [] as the opt-out.
Snap tests: vp-build-auto-output-restoration (dist restored on cache hit without a synthetic output config) and vp-build-auto-tracked-env (a VITE_ env change invalidates the cache and names the changed env). Edge cases live in vite-task.

Notes

The vite-task stack has landed on main; this PR now pins latest main (82ec12b2). Changelog diff for the latest repin: voidzero-dev/vite-task@68fb22e...82ec12b#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed
rolldown stays at main's pin (c462c7c5, v1.1.0), which is compatible with vite c13a37b53's rolldown 1.0.3 requirement.

netlify · 2026-06-06T17:08:35Z

✅ Deploy Preview for viteplus-preview ready!

Name	Link
🔨 Latest commit	`22f79af`
🔍 Latest deploy log	https://app.netlify.com/projects/viteplus-preview/deploys/6a3a348a76787700093756d5
😎 Deploy Preview	https://deploy-preview-1774--viteplus-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

socket-security · 2026-06-07T08:12:20Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/@voidzero-dev/vite-task-client@0.1.1
	npm/fresh-import@0.2.1
	npm/typescript-eslint@8.61.1
	npm/@vitest/utils@4.1.7 ⏵ 4.1.8
	npm/oxfmt@0.54.0
	npm/http-proxy-3@1.23.3
	npm/unrun@0.3.1
	npm/eslint-plugin-n@18.1.0
	npm/sass@1.101.0

View full report

github-actions · 2026-06-15T02:03:33Z

✅ Staging deployment successful!

Preview: https://viteplus-staging.void.app/
Commit: b35d839

liangmiQwQ · 2026-06-23T00:30:59Z

-        UserInputEntry::Auto(AutoInput { auto: true }),
+        UserInputEntry::Auto(AutoTracking { auto: true }),
        exclude_glob("!node_modules/.vite-temp/**", InputBase::Workspace),
        exclude_glob("!node_modules/.vite-temp/**", InputBase::Package),


According to https://discord.com/channels/1475973262193459293/1479410337223802951/1518498738413244446, these two lines which exclude .vite-temp config files could probably be safely removed, since the config files will be ignored automatically.

https://github.com/vitejs/vite/blob/403cc608e4e8633b0335f5e8221c83dfca4994f8/packages/vite/src/node/config.ts#L2652-L2655

…nvs) Vite reports its inputs/outputs/envs to the `vp` runner via `@voidzero-dev/vite-task-client`, so `vp build` no longer needs a hand-synthesized cache config. - Bump vite-task git deps to c44d7c33 (runner-aware IPC server/client + embedded napi addon); regenerate run-config.ts for the new task-config types. - Point the vite behind vp build/vp dev to latest vitejs/vite (c13a37b53), which carries the vite-task-client integration. vite lists vite-task-client in devDependencies, so it is bundled into vite's output (and thus into core) the same way as vite's other bundled deps (cac, esbuild, ...) — no extra dependency or build wiring needed. - Work around an upstream vite dts bug (vitejs/vite#21863): `node/index.ts` re-exports `KnownQueryTypeMap` but the type is declared without `export`, which breaks downstream type bundling (`vp build` MISSING_EXPORT). core's build adds the missing `export` when copying vite's type defs. - Remove vp build's synthetic cache config (env: [VITE_*], manual input excludes). All-None EnabledCacheConfig keeps caching enabled with auto input/output inference (output restoration); vp dev stays disabled. - Snap tests: vp-build-auto-output-restoration, vp-build-auto-tracked-env. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Repoints the vite-task git deps to the tip of the split stack (voidzero-dev/vite-task#431, the auto-output-track branch), whose crates tree is identical to the prior pin plus the runner env-change message refinement. Regenerates the two snapshots whose `VITE_*` cache-miss line now renders as "envs changed" (matching manual env config) instead of "tracked env glob 'VITE_*' changed". 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Picks up the cache-miss message refinement that now names the changed env var. Regenerates the two snapshots whose `VITE_*` cache-miss line reads `env 'VITE_MY_VAR' changed` / `env 'VITE_GREETING' changed` instead of the generic `envs changed`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

vite reports its transient bundled-config file under node_modules/.vite-temp to the task runner at runtime (ignoreInput/ ignoreOutput via @voidzero-dev/vite-task-client, vitejs/vite#22453), so the synthetic input excludes for pack/test/check are redundant. Keeps the OXLINT_TSGOLINT_PATH env tracking, results.json, !dist/**, and .vite/task-cache excludes unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Verify `vp run lint` and `vp run fmt` hit the cache on the second run. The lint fixture gitignores node_modules so oxlint does not fingerprint the runner's own node_modules/.vite/task-cache state; the fmt fixture sets an fmt config to avoid the non-deterministic "No config found" stderr-vs-stdout ordering. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

socket-security · 2026-06-23T07:25:28Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm `@typescript-eslint/eslint-plugin` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → `npm/typescript-eslint@8.61.1` → `npm/@typescript-eslint/eslint-plugin@8.61.1` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@typescript-eslint/eslint-plugin@8.61.1`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

wan9chi force-pushed the feat/vite-task-runner-tools branch from 83d8d81 to 6006f44 Compare June 6, 2026 19:11

wan9chi marked this pull request as ready for review June 6, 2026 19:21

wan9chi marked this pull request as draft June 7, 2026 00:39

wan9chi force-pushed the feat/vite-task-runner-tools branch 2 times, most recently from 2d380bf to a39a5d3 Compare June 7, 2026 01:22

wan9chi marked this pull request as ready for review June 7, 2026 01:29

wan9chi marked this pull request as draft June 7, 2026 01:30

wan9chi force-pushed the feat/vite-task-runner-tools branch 3 times, most recently from f3c2f78 to 0c7099a Compare June 7, 2026 02:38

wan9chi added the test: e2e Auto run e2e tests label Jun 7, 2026

wan9chi force-pushed the feat/vite-task-runner-tools branch from 0c7099a to 5285a43 Compare June 7, 2026 03:52

wan9chi force-pushed the feat/vite-task-runner-tools branch from baadc47 to 8f14d85 Compare June 8, 2026 02:13

wan9chi force-pushed the feat/vite-task-runner-tools branch from 6c9f8bf to 88a28a4 Compare June 15, 2026 02:47

fengmk2 reviewed Jun 15, 2026

View reviewed changes

Comment thread packages/core/build.ts

fengmk2 added this to the Beta milestone Jun 15, 2026

fengmk2 mentioned this pull request Jun 17, 2026

release: v0.2.0 #1856

Merged

gsmeira mentioned this pull request Jun 20, 2026

Task cache: a build with outDir under a tracked dir (e.g. Laravel public/build) never caches — emptyOutDir delete-probe counted as a read #1894

Open

4 tasks

wan9chi force-pushed the feat/vite-task-runner-tools branch 4 times, most recently from 52d8389 to db35a29 Compare June 21, 2026 14:06

liangmiQwQ reviewed Jun 23, 2026

View reviewed changes

wan9chi and others added 4 commits June 23, 2026 11:19

chore(deps): repin vite-task to latest main (82ec12b2)

164c870

wan9chi and others added 11 commits June 23, 2026 11:19

docs: clarify zero-config vp build caching

dd52604

fix: guard vite type export workaround

e66e105

chore(deps): use vite 8.1.0-beta.0

46b7cca

chore: dedupe pnpm lockfile

9572741

test: update vite build banner snapshots

96dfd59

fix: sanitize migrated oxlint rule options

ba30ecf

ci: verify cacheable monorepo task hits

89dd4ce

chore: bump vite-task to 89613544

f649e97

chore: bump vite-task to 8daa9bb7

9139389

wan9chi force-pushed the feat/vite-task-runner-tools branch from db35a29 to 22f79af Compare June 23, 2026 07:23

fengmk2 linked an issue Jun 23, 2026 that may be closed by this pull request

Task cache: a build with outDir under a tracked dir (e.g. Laravel public/build) never caches — emptyOutDir delete-probe counted as a read #1894

Open

4 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: integrate vite-task runner-aware tools (auto output + tracked envs)#1774

feat: integrate vite-task runner-aware tools (auto output + tracked envs)#1774
wan9chi wants to merge 15 commits into
mainfrom
feat/vite-task-runner-tools

wan9chi commented Jun 6, 2026 •

edited

Loading

Uh oh!

netlify Bot commented Jun 6, 2026 •

edited

Loading

Uh oh!

socket-security Bot commented Jun 7, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jun 15, 2026 •

edited

Loading

Uh oh!

Uh oh!

liangmiQwQ Jun 23, 2026 •

edited

Loading

Uh oh!

socket-security Bot commented Jun 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

wan9chi commented Jun 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

Notes

Uh oh!

netlify Bot commented Jun 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for viteplus-preview ready!

Uh oh!

socket-security Bot commented Jun 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Jun 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

liangmiQwQ Jun 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

socket-security Bot commented Jun 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

wan9chi commented Jun 6, 2026 •

edited

Loading

netlify Bot commented Jun 6, 2026 •

edited

Loading

socket-security Bot commented Jun 7, 2026 •

edited

Loading

github-actions Bot commented Jun 15, 2026 •

edited

Loading

liangmiQwQ Jun 23, 2026 •

edited

Loading