A key with nothing to run

Inputs can lack a command association. Test fixtures, a shared configuration, or a dependency source needing no build require re-running when they modify, yet they do not necessitate running independently. A group task can now incorporate such a key: // vx.config.ts import { defineProject } from '@vzn/vx/config' export default defineProject ({ tasks : { fixtures : { cache : { inputs : { files : [ fixtures/** ] }, outputs : { files : [] } } }, test : { exec : { command : 'bun test' }, dependsOn : [ fixtures ], cache : { inputs : { files : [ src/** , tests/** ] }, outputs : { files : [] } }, }, }, }) Altering a fixture file causes test failure, whereas modifying any other element triggers re-run.

Fixtures launch no process, produce no cache entry, and do not factor into the run summary. --affected behaves like other edge cases. Migration of Nx and Turbo repositories necessitates this. Nx tags a task based on its dependencies, even for production files, while Turbo hashes a transit node per package. @vzn/vx-migrate previously treated each as a running task: true.

TanStack/query led to vx executing 36 tasks, compared to Nx's 25. These tasks now share identical keys, operate without processes, and maintain the same task count as Nx. First published on the vx blog. vx serves as an MIT task runner and build cache for JavaScript monorepos: vznjs.github.io/vx · GitHub. Developed with AI assistance.