$ the-wire · showcase
Turborepo native lockfile fallback, faster SST lookups
By RepoJournal · Filed · About Vercel
Turborepo now tolerates missing native lockfiles while Next.js cuts hash lookups in its storage layer.
Turborepo now gracefully handles native lockfile failures [1], so Cargo and uv package graphs remain available even when their lockfiles are missing, stale, unreadable, or unparsable. The fix keeps frozen/locked execution semantics and preserves hard failures for non-lockfile safety violations. For Factory users, a new coding-agent selector adds fx, Claude Code, Codex, Cursor, OpenCode, and Pi support [2], with Cursor retaining its adapter-native authentication. The Factory chat surface was rebuilt with optimistic messages and Streamdown rendering [3], and workspace failures now show actionable details that survive reloads [4]. In Next.js, the `popular` workflow and its `next-repo-actions` action were deleted [5], as the maintainer agent now handles that reporting. A storage optimization [6] changes key-order sorting for short keys (≤ 32 bytes) in SST blocks, eliminating the need to recompute xxh3 hashes during binary search, roughly ten hashes per lookup. This ships in v16.4.0-canary.12 [7].
Action items
- → Update Vercel Connect subscription to include pull_request events if you depend on merged PR Slack updates vercel/turborepo [monitor]
- → Review native lockfile handling if you use Turborepo with Cargo or uv vercel/turborepo [monitor]
- → Test the SST block key-order change in your Next.js deployment vercel/next.js [plan]
References
- [1] fix: Gracefully handle native lockfile failures ↗ vercel/turborepo
- [2] chore: Add selectable Factory coding harnesses ↗ vercel/turborepo
- [3] chore: Improve Factory chat streaming ↗ vercel/turborepo
- [4] fix: Show workspace failure details ↗ vercel/turborepo
- [5] [ci] Remove the popular workflow and its action ↗ vercel/next.js
- [6] Store keys in key order in SST blocks that omit hashes ↗ vercel/next.js
- [7] v16.4.0-canary.12 ↗ vercel/next.js