$ the-wire · showcase
TURBOREPO FIXES PNPM LOCKFILE BREAKAGE, ADDS HEAP PROFILING
By RepoJournal · Filed · About Vercel · Composed from the cited sources · methodology
1 person shipped this
Turborepo 2.9 now preserves pnpm injected peer dependencies during prune operations, fixing a critical lockfile corruption bug that broke frozen installs in Docker builds.
The pnpm fix [1] addresses a silent failure where turbo prune would drop base package entries needed to resolve peer-variant snapshot keys, leaving pruned lockfiles unable to install with --frozen-lockfile. This one's especially dangerous because it only surfaces at deploy time. In parallel, heap allocation profiling [2] shipped opt-in DHAT support to the Rust CLI, giving you a repeatable way to find and validate memory hotspots without custom instrumentation. The profiler outputs raw JSON plus ranked summaries by bytes and allocation count. On the observability front, OTel duration histograms got Turborepo-specific bucket boundaries [3] that actually cover real build durations instead of maxing out at 10 seconds, making P50/P95 queries and Grafana heatmaps usable again.
Action items
- → Upgrade turborepo to 2.9.15+ before next Docker build if using pnpm with workspace dependencies vercel/turborepo [immediate]
- → Test heap profiling with --heap flag on your next optimization pass vercel/turborepo [plan]
- → Monitor OTel duration metrics for improved observability across your CI pipelines vercel/turborepo [monitor]
References
- [1] fix: Preserve pnpm injected peer package entries ↗ vercel/turborepo
- [2] feat: Add heap allocation profiling ↗ vercel/turborepo
- [3] fix: Use build-scale OTel duration buckets ↗ vercel/turborepo
