pnpm opens the workspace to Cargo and Python as Turborepo tunes for speed

One workspace, many ecosystems

The week's biggest shift came from pnpm, which stopped treating JavaScript as the only citizen of a monorepo. pnpm 12.4 now installs crates and Python packages next to npm packages in the same workspace, so a repository can build a Rust crate, a Python package, and a handful of npm libraries under one dependency graph. The same release adds pnpm pipeline to run a workspace's tasks the way a CI job would, ships binaries for six more platforms, and pairs with pnpr 0.1.0-alpha.11, which serves Cargo, Python, and container registries beside npm, publishes across all of them in one transaction, and signs users in through OIDC. For teams that have been gluing together Cargo, pip, and pnpm invocations in CI scripts, that consolidation is the headline of the week.

Turborepo's performance and correctness sweep

Turborepo shipped a run of canaries that reads less like a feature drop and more like a sustained tuning pass. The most substantive work was in performance across the resolver, cache, and watch paths: reusing resolver inference during file tracing, cutting memory during remote-cache transfers, caching LSP task indexes, and reusing the package graph across partial watch reruns. The same stretch of releases brought Cargo root package support and Cargo tasks that stay runnable without compiler identity, plus a skipPackageGraph option for @turbo/repository's Workspace.find and a tar bump for CVE-2026-73566 — the one genuinely security-relevant item in the batch.

Correctness fixes followed close behind. Turborepo restored leading flags on implicit run commands and folded experimentalCI into task hashes, so cache keys reflect the flag, while turbo ls stopped cloning the package list. Lockfile handling got attention too: Yarn resolution declaration order and nested Bun package keys are now preserved, and duplicate interrupts during task shutdown were suppressed. Most recent of the run, native task dependencies are no longer lost across entrypoints, and LOCALAPPDATA passes through by default — a small change that matters to Windows users with relocated caches.

A trace view for VS Code

Vitest's editor integration got a debugging upgrade: Vitest VS Code v1.52.0 adds a trace view for inspecting runs without leaving the editor. The same update fixes compatibility with Vitest 5's testNamePattern format and repairs the legacy AST collector, which had been ignoring computed member calls from esbuild's using helper — the kind of quiet mismatch that makes tests silently fail to register.