docs: per-phase operation comparison — Turbo vs Nx vs vx#97
Open
Exelord wants to merge 3 commits into
Open
Conversation
d77e2d1 to
ff0dc48
Compare
Exelord
pushed a commit
that referenced
this pull request
May 17, 2026
PR #100's CI failed on format-check because the new docs (patterns.md, benchmarks.md) used inconsistent column padding in markdown tables. PR #96 / #97's monorepo-structure.md regressed the same way. `bun src/bin.ts run format` rewrites all three to oxfmt's canonical table alignment. No content changes.
Captures what each runner does at each step of a `vx run` invocation. Companion to the integrity-audit doc (PR #96): that one is "what's wrong", this one is "what's everyone doing". Structure: - Quick-scan summary table (14 phases × 3 runners) - Per-phase deep dives (14 sections, each with its own table + callout for where we have a gap vs Turbo/Nx) - Cross-links to comparison.md (feature backlog) and the integrity audit (correctness backlog) Sources pinned to revisions: - Turbo: /tmp/turbo at 71f8c90 - Nx: /tmp/nx at 962f146 - vx: main Daemon paths in Nx deliberately excluded — we're daemonless by design. This is reference / context, not a backlog. When `main` moves, the vx column moves with it.
dd9f028 to
a42b0dc
Compare
Exelord
pushed a commit
that referenced
this pull request
May 17, 2026
PR #100's CI failed on format-check because the new docs (patterns.md, benchmarks.md) used inconsistent column padding in markdown tables. PR #96 / #97's monorepo-structure.md regressed the same way. `bun src/bin.ts run format` rewrites all three to oxfmt's canonical table alignment. No content changes.
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
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.
Summary
Per-phase operation breakdown comparing Turbo, Nx, and vx side-by-side. Companion to PR #96 (integrity audit) — that one is "what's wrong", this one is "what's everyone doing at each step".
Structure
Every gap cell links to either
comparison.md(feature backlog) orintegrity-audit-2026-05.md(correctness backlog) — so the table doesn't accumulate floating TODOs.Sources
Pinned to specific revisions so future diffs are reproducible:
/tmp/turboat71f8c90/tmp/nxat962f146mainDaemon paths in Nx deliberately excluded — we are daemonless by design (
docs/design/monorepo-structure.mdrecords this).Notable findings on a re-read
vx.config.tsevery time. Could be a follow-up if cold start becomes a complaint.File
docs/design/runner-comparison-2026-05.md(246 lines)Test plan
bun src/bin.ts run formatcleanhttps://claude.ai/code/session_016HXj6HW6bxSn8EYuKcxTD9
Generated by Claude Code