feat: integrate vite-task runner-aware tools (auto output + tracked envs)#1774
Draft
wan9chi wants to merge 3 commits into
Draft
feat: integrate vite-task runner-aware tools (auto output + tracked envs)#1774wan9chi wants to merge 3 commits into
wan9chi wants to merge 3 commits into
Conversation
✅ Deploy Preview for viteplus-preview canceled.
|
wan9chi
force-pushed
the
feat/vite-task-runner-tools
branch
from
83d8d81 to
6006f44
Compare
wan9chi
force-pushed
the
feat/vite-task-runner-tools
branch
2 times, most recently
from
2d380bf to
a39a5d3
Compare
wan9chi
force-pushed
the
feat/vite-task-runner-tools
branch
3 times, most recently
from
f3c2f78 to
0c7099a
Compare
…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>
wan9chi
force-pushed
the
feat/vite-task-runner-tools
branch
from
0c7099a to
5285a43
Compare
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)
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
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)
wan9chi
force-pushed
the
feat/vite-task-runner-tools
branch
from
baadc47 to
8f14d85
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Integrates the runner-aware-tools work from vite-task PR voidzero-dev/vite-task#410: Vite reports its inputs/outputs/envs to the
vprunner via@voidzero-dev/vite-task-client, sovp buildno longer needs a hand-synthesized cache config (enabling auto output restoration and auto tracked envs).Changes
6e634c65(voidzero-dev/vite-task#410): runner-aware IPC server/client + embedded napi addon, andSession::mainreturningExitStatus. Regenerate the napi binding (RunnerClient/loadexports) andrun-config.tsfor the new task-config types.vp build/vp devto latest vitejs/vite (c13a37b53), which carries the vite-task-client integration. vite lists@voidzero-dev/vite-task-clientin 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.vp build's synthetic cache config (env: ["VITE_*"], manual input excludes). The all-NoneEnabledCacheConfigkeeps caching enabled with auto input/output inference (output restoration); vite'signoreInput/ignoreOutput/getEnv/getEnvsrefine the fingerprint at runtime.vp devstaysdisabled().vp-build-auto-output-restoration(dist restored on cache hit without a syntheticoutputconfig) andvp-build-auto-tracked-env(aVITE_env change invalidates the cache, reported ascache miss: tracked env glob 'VITE_*' changed). Edge cases live in the vite-task PR. A couple of existing snapshots updated for the new runner-aware cache-miss messages.Notes
6e634c65); land that PR first.c462c7c5, v1.1.0), which is compatible with vite c13a37b53's rolldown1.0.3requirement.🤖 Generated with Claude Code