Can't install it using pnpm 11

[ap32]

shadcn-vue init fails after CSS variables are updated. I found that the CLI is spawning pnpm, but the resolved pnpm version inside the spawned process is 10, even though the target project uses pnpm 11. Result is store conflict. Can I bypass that somehow as temporary fix, maybe force pnpm 11?

[TargiX]

This was a CLI package-manager detection/install issue rather than an incompatibility with pnpm 11.

Two fixes landed after the behavior described here:

• f2e3552 routes init dependency installs through the detected package manager and checks the lockfile, packageManager field, .pnpm directory, and the parent pnpm dlx user agent.
• df5d0b9 switched the install path to nypm while preserving that detected manager.

They are included in shadcn-vue v2.7.4, so the current workaround is simply to run the fixed CLI with pnpm 11 active:

corepack enable
corepack use pnpm@11
pnpm dlx shadcn-vue@2.7.4 init

Keeping a concrete pnpm 11 version in the project's packageManager field also lets Corepack select the same version for child installs.

If an earlier failed run already mixed a pnpm 10 installation into node_modules, reinstall that project's dependencies with pnpm 11 before rerunning init; otherwise the existing store-location mismatch can remain even though the CLI itself is fixed.