pnpm's two CLIs converge, Bun patches, and Vitest 5 lands

Two pnpm CLIs, one feature set

pnpm spent the week closing the gap between its two implementations. The Rust-based CLI picked up catalog support for the workspace: protocol, supply-chain flags on remove and update, project-aware global commands that now run as real executables, and a return to the system resolver for hostname resolution on Linux and Windows — plus noticeably faster installs on large workspaces. The JavaScript CLI then caught up to that same baseline, leveling the two implementations on catalogs, supply-chain flags, and pnpm deploy without injected dependencies. The practical upshot for anyone migrating between the two: the workspace and catalog semantics you rely on no longer change depending on which pnpm you happen to be running. pnpm change check also arrives as a CI-friendly gate for verifying changelog entries.

Vitest 5 ships, and static parsing becomes the default

Vitest 5 is out, and the headline is speed: the release reworks the test pipeline around performance while clearing out long-standing bugs, and it swaps loupe.inspect for pretty-format in its assertion output. The groundwork for that landed in the final release candidate, where vitest list began parsing test files statically by default instead of executing them just to enumerate tests — a change that matters most in large suites, where discovery used to cost real time before a single test ran. The same candidate promoted clearCache out of experimental and added a link from the UI straight to Playwright traces. Both changes are breaking in the quiet way: if you depended on vitest list actually running your files, or on clearCache being gated behind a flag, check your setup before upgrading.

Bun's patch week

Bun shipped two consecutive patch rounds, one and then another, drawing on contributions from a handful of outside developers alongside the core team. Neither release carries a headline feature — this was consolidation work, the kind of week where a runtime fixes what the previous release disturbed and tightens up edges rather than expanding its surface. If you're on Bun already, upgrading is routine; if you're evaluating it, nothing here changes the calculus.

The week in short

The through-line across all three projects is parity and consolidation rather than new surface area. pnpm unified two CLIs that had drifted apart, Vitest rebuilt its discovery path before declaring 5.0 stable, and Bun spent its week stabilizing. For teams running mixed toolchains, the pnpm work is the one with immediate consequences: fewer behavioral surprises between the JavaScript and Rust builds means fewer CI-only failures that don't reproduce locally.