PKG0008Install one copy of each singleton package
Why it happens
Two versions of a singleton are two module instances. Vue, Pinia, Nuxt and React keep their state per instance, so code from one copy cannot see the other's injections, stores or app context, and h3 and Drizzle reject objects created by the other copy. A lockfile resolves the second copy when one package pins a version or a range that excludes the app's.
Fix
Update the package that resolves the extra version so it accepts the version the rest of the install uses, ideally as a peer, or add a pnpm override for that version and run pnpm install. Doctor reports each duplicate where it enters the workspace, at the package.json entry that leads to it.
Example
Override a transitive pin to the app's Vue
Before
# pnpm-lock.yaml resolves vue 3.5.44 and, through old-ui, vue 3.4.0
After
# pnpm-workspace.yaml
overrides:
vue: 3.5.44
Verify the fix
Run only this rule after editing so the report stays focused on the diagnostic you are closing:
pnpm vite-doctor . --extends package/recommended --rules package/no-duplicate-singleton