vx on real repos
The benchmark on vx vs Nx is a synthetic graph built to be fair to every tool. This page is the other half: real public repos, moved to vx with one command and timed against the tool they already use.
TanStack/query, against Nx
Section titled “TanStack/query, against Nx”TanStack/query at commit 817bd02,
the build tasks without examples and integrations: 25 tasks for each
tool.
| Case | vx | Nx | vx is |
|---|---|---|---|
| Cold build | 34.6 s | 39.4 s | 14% faster |
| Restore from cache | 0.39 s | 1.26 s | 3.2× faster |
| Nothing changed | 0.22 s | 1.43 s | 6.5× faster |
“N% faster” means Nx takes N% longer. Restore deletes the build outputs and keeps the cache; “nothing changed” deletes nothing.
Run 2026-10-09 on linux x64, 4 cores: vx 0.0.633 configured by
vx init --native, Nx 23.2.1 with the daemon off and no Nx Cloud, pnpm
12.4.2. 5 workers each, best of three interleaved runs. Every run is in
the benchmarks.
Try it on yours
Section titled “Try it on yours”npm install -D @vzn/vxnpx vx init --keep--keep writes one file, vx.workspace.ts, which reads your
turbo.json or Nx graph as it is: nothing in the repo changes. Run
vx run build --all next to the tool you use today. To undo, delete
vx.workspace.ts. When you want native config, vx init --native
writes a vx.config.ts per package; Migrate
walks through it.
More repos join this page as they are measured, each with its commit, versions and machine.