BetaWeekly digests are a beta — we're trying something new. Feedback welcome.
pnpm tightens security and offline installs while Turborepo speeds up setup
November 9–15, 2026
pnpm closed out the week with a security fix that stops registry credentials and URL placeholders from leaking, alongside faster offline installs and lockfile stability; Turborepo made turbo.lock creation about ten times faster and moved managed tool installs into a shared store.
The week at a glance
Replay the weekpnpm hardens security and offline workflows
pnpm's week split between security fixes and making offline and remote installs behave predictably. The security work landed in two lines at once: a ${VAR} placeholder in a repository's registry URL now fails the command instead of silently routing requests to another registry, and offline install errors no longer print registry credentials. The bundled node-gyp also stopped shipping the undici version that security scanners flag, on both the 11.x and 12.x lines.
Offline installs got real capability rather than just safety. pnpm store add now prepares tarball and git dependencies for offline installs, so a project can download its pinned tarballs ahead of time and then --offline cleanly. The experimental v13 lockfile now records the specifiers of local directory dependencies, and repeated installs keep their peer dependency choices instead of re-resolving them.
The 12.x line also added pnpm fund for listing funding URLs, a projectScopedOptionalPeers setting, an experimental JSON lockfile format, and a loaded node linker that handles packages needing a build. Elsewhere the week was bug-fix churn across nodeLinker: hoisted, pnpm deploy, frozen lockfiles, and overrides; if a pnpr server refuses a setting, pnpm now resolves locally. Note the compatibility floor: remote resolution and shared build caches need pnpr 0.1.0-alpha.20 or newer.
Turborepo: faster setup and safer credentials
Turborepo's headline is speed. Creating turbo.lock is about 10x faster, and turbo setup now installs managed tools into a shared content-addressed store under ~/.local/share on macOS — so the second project on a machine reuses what the first already downloaded. That same release tightened the trust boundary: credentials saved for Vercel are now restricted to Vercel endpoints, so they can't be sent elsewhere. turbo query can also expose a task's hash and log file, which is useful when debugging why a cache hit or miss happened.
A canary followed with directory links now bounded in manual input hashing — a correctness fix for projects hashing directories directly rather than through the standard pipeline. Worth knowing about, but canary users only.
What it means for your week
Together the two products moved in the same direction: fewer surprise network round-trips, stricter boundaries around secrets, and faster cold starts. If you run monorepos with remote caches or depend on reproducible offline installs, both upgrades are worth taking — just check your pnpr server version first.