
Watch hears a directory made again
vx watch keeps hearing a directory that was removed and made again, as git stash and a branch switch do. A damaged cache file is named with its remedy, and distributed runs end tasks sooner.
vx init writes configs that run on real Nx, pnpm and Next.js workspaces. vx watch hears every edit made during its first run, the cache keeps only bytes its key names, and distributed task execution plans with one engine.

vx init was run on more than twenty well-known open source workspaces.
Each gap it hit is fixed, so the configs it writes now lock and run there.
vx watch hears an edit made while its first run is going. The cache
refuses bytes its key does not name.
Distributed task execution plans with one engine. This release has breaking changes: read Breaking changes first.
In this release
A config vx init writes must run on the first try. On real workspaces
some did not: a name pnpm could not link, an output outside the project,
a formatter the workspace does not use.
Each workspace below found a gap, and each is fixed:
tsconfig its written config
would break.pnpm install after its own
pnpm add.tshy build stays cached across its manifest
rewrite, and two tasks sharing dist keep the right one cached.See Migrate.
vx watch has no watcher during its first run. An edit made then could
be taken for the run’s own write, or missed when committed or stashed.
The output stayed built from the old bytes until the next save.
The first run records git’s index and every task’s key. When the watcher arms, a moved key starts a cycle.
Here src/a.txt is edited one
second into a two-second first build, and the cycle builds it:
$ vx watch build --all Tasks status cache ±usual time cpu mem outputs blocks worker task success miss −1ms 2.01s 0% 3.6MB 10B 0 local packages/app#buildwatching 1 project · 1 task
changed packages/app#build inputs, edited during the first run Tasks status cache ±usual time cpu mem outputs blocks worker task success miss −6ms 2.01s 0% 3.6MB 10B 0 local packages/app#buildA task that rewrites its own input in place (sort -o, sed -i) ran
about nine cycles a second, forever. Watch now settles on that rewrite and
says once why:
vx watch: packages/app/src/list.txt is rewritten in place by its own task every run, so its rewrite starts no cycle. Set inputs.stability: { strategy: 'mutable' } to cache that task.See Running tasks.
A stale hit replays wrong bytes under a green run, so the cache now refuses to save what its key does not describe:
vx why names vx-version.When a cached task’s clean deletes files a task before it wrote, vx now says which and who wrote them:
$ vx run build --all Tasks status cache ±usual time cpu mem outputs blocks worker task success no-cache +2ms 9ms 33% — — 1 local packages/lib#types Warnings [vx] packages/lib#build: its outputs' clean before it ran deleted dist/index.d.ts, which packages/lib#types wrote earlier in this run — declare it in packages/lib#types's outputs, or have packages/lib#types write outside packages/lib#build's outputs Tasks status cache ±usual time cpu mem outputs blocks worker task The local store now keeps an entry past 2 GiB (a Next.js standalone build), and an absolute link into the workspace is cached as relative.
See Caching.
With @vzn/vx-dte, one forecast and one objective now place and size
every run: the earliest end, then the least core time held, then the
fewest workers.
vx dte worker, after checkout and
install. Run vx dte init again to rewrite both workflows.ideal is the best end the run’s worker limits allow;
the uncapped end is the new perfect line.See Distributed task execution.
strace to install, and a task spawning many processes no longer slows down under it. VX_DEBUG_STRACE=1 uses strace.@vzn/vx-lockfile reads pnpm’s v13 lockfile format.@vzn/vx-history sends task timings to the history server while the run goes, not only at its end.yarn vx and package scripts calling vx start under Yarn 2+, Plug’n’Play included..gitattributes selects every project under it with --affected.package.json saved with a UTF-8 BOM keeps its workspaces’ ranges in the key.node_modules linked to a directory outside the workspace stays on a sandboxed task’s PATH.@vzn/vx type-checks under a plugin author’s own tsconfig.@vzn/vx-cache asks for a download again after a reset connection.package.json no longer orders, keys or --affected-selects other projects: declare it in each project that loads it.@vzn/vx ships launcher.cjs, not launcher.sh, as its bin.dte({ scheduler }) is removed.parent input and github()’s adopt of workers a step started are gone: run vx dte init again.DteAdapter’s cancel() gets no late argument, and kept() is no longer called.@vzn/vx-cache-server names objects by hashed issuer, repository and ref: artifacts stored under the old names are not read. blobName() is async.See Upgrading.
vx upgrade