Summary & Key Takeaways ​

• pnpm 11 Beta 3 introduces a new store format where runtime dependencies are always linked from a global virtual store.
• The index file format is optimized to store hash algorithms once per file and uses hex digests for improved performance during path lookups.
• The store version is bumped to v11, and bundled manifests are now stored directly in the package index file to reduce I/O and speed up installations.
• SQLite is now used for storing the package index in the content-addressable store, replacing individual JSON files with a single database for better performance and space efficiency.
• Global installs and pnpm dlx now default to using the global virtual store, with packages stored in a shared links directory.
• Globally installed packages are now isolated, each receiving its own installation directory to prevent conflicts and ensure consistent environments.

Our Commentary ​

These changes in pnpm 11 Beta 3 are genuinely exciting. The move to SQLite for the package index and the optimized file format are huge for performance, especially on systems with high I/O overhead. But what really stands out to us is the concept of isolated global packages. This is a game-changer for managing global tools and avoiding the 'it works on my machine' syndrome that often plagues shared environments. It feels like pnpm is doubling down on its core strengths, pushing the boundaries of what a package manager can do for developer experience and reliability.