The Wire · Showcase
TURBOREPO CUTS VENDOR BLOAT, FIXES GITIGNORE PRECEDENCE BUG THAT BROKE NEXT.JS HASHING
By RepoJournal · Filed · About Vercel
Turborepo shipped three critical fixes overnight: ditching 10k lines of vendored Ghostty bindings, restoring the devtools command that broke in production, and correcting gitignore precedence that caused task hash mismatches in Next.js projects.
The biggest structural win is Turborepo's switch to upstream libghostty-vt crates [1], eliminating a 10k-line maintenance burden from the codebase while improving terminal integration reliability. But the real fires this cycle are the devtools regression [2] and the gitignore precedence inversion [3]. The devtools fix is straightforward: a local decision override accidentally bypassed the Vercel Flags adapter, breaking turborepo.dev/devtools discovery. The gitignore bug is nastier. Turborepo was inverting git's precedence rules, so a root-level `*.log` ignore would override a deeper `!important.log` whitelist, silently dropping files from task hashing and dirty checks. Next.js projects hit this hard. In parallel, Turborepo shipped mimalloc as the default allocator [5], cutting malloc overhead by 12-15% across the entire run, and patched Windows test flakes with nextest retry logic [4]. Over on the AI side, Deepseek and Anthropic got fixes: Anthropic now properly forwards `thinking: { type: 'disabled' }` to the API [6] instead of silently dropping it, and Deepseek's type-checking no longer chokes on internal.d.ts [7]. The Vercel CLI got a housekeeping pass with agent-runs and five missing commands restored to root help output [8].
Action items
- → Upgrade Turborepo to pick up gitignore precedence fix and Ghostty refactor vercel/turborepo [immediate]
- → If using `turbo devtools`, pull the latest CLI version to restore the command vercel/turborepo [immediate]
- → Verify Anthropic reasoning config if using `type: 'disabled'` explicitly vercel/ai [plan]
- → Upgrade Deepseek provider for type-checking stability vercel/ai [plan]
References
- [1] refactor: Use upstream libghostty-vt crates instead of vendored bindings (#13205) vercel/turborepo
- [2] fix: Remove devtools feature flag (#13219) vercel/turborepo
- [3] fix: Correct gitignore precedence in untracked walk and memoize matcher chains (#13221) vercel/turborepo
- [4] ci: Retry Windows nextest aborts from transient 0xc0000142 spawn failures (#13240) vercel/turborepo
- [5] perf: Use mimalloc as the global allocator (#13237) vercel/turborepo
- [6] fix(anthropic): forward thinking { type: 'disabled' } to the API (#16687) vercel/ai
- [7] fix(deepseek): exclude internal.d.ts from typecheck ↗ vercel/ai
- [8] [email protected] ↗ vercel/vercel
FAQ
- What changed in Vercel on July 4, 2026?
- Turborepo shipped three critical fixes overnight: ditching 10k lines of vendored Ghostty bindings, restoring the devtools command that broke in production, and correcting gitignore precedence that caused task hash mismatches in Next.js projects.
- What should Vercel teams do about it?
- Upgrade Turborepo to pick up gitignore precedence fix and Ghostty refactor • If using `turbo devtools`, pull the latest CLI version to restore the command • Verify Anthropic reasoning config if using `type: 'disabled'` explicitly
- Which Vercel repositories shipped on July 4, 2026?
- vercel/turborepo, vercel/ai, vercel/vercel