# Automatic pnpm v10 support

By Steven Van · 2025-02-28

Projects with a pnpm lockfile version 9.0 get v10 if they are new, while existing ones stay on v9 unless pinned with Corepack.

New pnpm projects on [Vercel](<https://creatorstoolbox.com/tools/vercel>) now build with pnpm v10 automatically. This applies to projects with a pnpm-lock.yaml file that has lockfileVersion: '9.0', and covers both the Install and Build Commands.

Existing projects stay on pnpm v9 for backwards compatibility. pnpm v9 also writes lockfileVersion: '9.0', so the lockfile alone can't tell the two versions apart. The [package managers documentation](<https://vercel.com/docs/deployments/builds/package-managers#supported-package-managers>) says newer projects prefer pnpm 10 and older ones prefer pnpm 9. The build logs show which version a given deployment used. To move an existing project up to v10, or to pin a new one back to v9, use Corepack.

![Vercel](<https://www.google.com/s2/favicons?domain=vercel.com&sz=128>)

Vercel

The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.

[View Vercel →](<https://creatorstoolbox.com/tools/vercel>)

[Original source](<https://vercel.com/docs/deployments/builds/package-managers#supported-package-managers>)

[Read Automatic pnpm v10 support on Creators Toolbox](<https://creatorstoolbox.com/blog/vercel-automatic-pnpm-v10-support>)

---
Canonical source: https://creatorstoolbox.com/blog/vercel-automatic-pnpm-v10-support