Vitest beta rethinks config, Turborepo stable courts Cargo

Vitest beta separates config from server

The week’s biggest story is Vitest’s v5.0.0-beta.7, which breaks config resolution away from the server object. Programmatic users who previously relied on startVitest() or createVitest() to return a fully configured server will need to migrate: config is now resolved independently before the server is created. The change, driven by @sheremet-va, cleans up Vitest’s internals but means any custom launcher or test runner wrapper must update its call sites. On the upside, the beta ships a pluggable benchmark provider API, a togglable injectCjsGlobals option, and performance wins from warm modules, Node compile cache, and bundled dependencies. The VS Code extension also saw a small but welcome quality-of-life fix: diagnostics are now tagged with source "Vitest" instead of the default, making them filterable in the Problems panel.

Turborepo matures with Cargo support and polish

Turborepo reached a minor milestone with v2.10.6, which now supports Cargo-only repositories — Turborepo automatically infers Cargo workspace tasks, so Rust monorepos can use its caching and orchestration without a JavaScript package manager. The release also fixes a batch of pruning bugs (Bun, Yarn, pnpm), resolves security audit vulnerabilities, and preserves TUI output colors. The canary track continued to add refinements: v2.10.6-canary.5 preserves pnpm node@runtime: lockfile entries that were previously dropped and checks dynamic imports in the boundaries module, while v2.10.7-canary.1 fixes JIT input matching for affected tasks and preserves pnpm root and aliased dependencies during prune. The latest v2.10.8-canary.1 adds multiple macOS file watch root support and enables mouse wheel scrolling in the Terminal UI task list — small ergonomic wins that add up. (A subsequent v2.10.8-canary.2 was purely internal refactoring.)

Deno fixes registry downloads

Deno v2.9.4 fixed a critical bug: npm tarballs were downloading from registry.npmjs.org instead of the configured registry. If you use a private npm registry or mirror, this was silently breaking your dependency resolution. The release also includes dozens of other fixes across the runtime, plus V8 upgrade to 150.2.0.