Shim for `pnpm` & `yarn`

[chungweileong94]

Description

Currently, if I install vite-plus globally, it works great for the most part, but as soon as I use any AI agent, the problem starts to show up, where the agent will attempt to use pnpm/yarn instead of vp, which is something already solved in the project-level AGENTS.md vite-plus section. However, if other teams don't have Vite-plus installed globally, their agent will tend to use vp and result in a command not found.

The only workaround is to disable the vp env, and use fnm/nvm + corepack to manage my node/package manager.

Suggested solution

Have a shim for both pnpm and yarn, then let Vite+ resolve the correct version of the pnpm/yarn, just like how node, npm & npx shims work.

Alternative

No response

Additional context

No response

Validations

• Read the Contributing Guidelines.
• Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
• Check that there isn't already an issue requesting the same feature.

[fengmk2]

You can use vp to install a global pnpm vp install -g pnpm, and see if this effect meets your application scenario.

[chungweileong94]

You can use vp to install a global pnpm vp install -g pnpm, and see if this effect meets your application scenario.

Yes, but it doesn't work quite the same as I wanted from corepack, where I don't think it will use the correct version as I specify in package.json.

[chungweileong94]

So I'm not sure why I didn't think about this one before, but another better workaround is to install corepack globally, and both pnpm and yarn will just work, pretty great so far. But still, not sure if this can be part of the Vite+.

[fengmk2]

@chungweileong94 Previously, corepack support wasn't considered because it's no longer built-in starting from Node 25+, but we can indeed consider adding corepack to the default shims tool list