Repository navigation
Forward various commands using vp pm #1038
Description
Description
I am looking to introduce Vite+ into an existing project that uses pnpm. However, in our project, we perform a minimal dependency resolution during the container build using pnpm deploy. When I try to execute the pnpm deploy command via vp pm, I get the error: Command 'deploy' not found.
If the vp pm command could forward all commands to the package manager, it would make the transition to Vite+ much smoother.
Suggested solution
The vp pm command should forward all subcommands to the package manager.
Alternative
In my use case, being able to run the vp pm deploy command would allow for a smooth transition to Vite+.
Additional context
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.
Reacted by Ray and Rúben Ferreira
Activity
cpojer commentedon Mar 20, 2026
We don't support every single package manager command as we aim to provide a common interface across all package managers.
deployis implemented by some, but not by all.If you rely on pnpm's deploy command, I suggest defining a
deployscript that doespnpm deploy. Then you can usevp run deploy.thinceller commentedon Mar 20, 2026
This workaround seems like it will work well.
Thank you for the response.
thinceller commentedon Mar 21, 2026
@cpojer By the way, the documentation for the vp pm command states the following:
vite-plus/docs/guide/install.md
Line 122 in d62e5d9
As you explained,
vp pmprovides a common interface that works across multiple package managers rather than forwarding commands directly. In fact, the "forwards directly" wording is part of what led me to expect thatvp pm deploywould work.Would it be worth updating the documentation to more accurately describe what vp pm does?
cpojer commentedon Mar 23, 2026
Yes that is a good point and we might be repeating this incorrectly in a few places across the repo. Do you wanna send a PR?
GoodbyeNJN commentedon May 16, 2026
@cpojer I firmly believe this feature is necessary.
But in fact, version v0.1.21 introduced a dedicated
vp pm pluginsubcommand specifically foryarn, which actually contradicts what you said about "provide a common interface across all package managers." Since a special case has already been created foryarn, should special cases also be created fornpm x,pnpm y, andbun z? Instead of creating special cases for various possible user needs in the future, it's better to directly support transparent forwarding.So I propose:
vp pm <cmd> [options], first check ifcmdis a known commandcmdandoptionsto the package manager under the hood, whethercmdandoptionsare valid should be confirmed by the user themselvesfengmk2 commentedon May 18, 2026
@jong-kyung
vp pm pluginbroke this rule, we need to revert #1540jong-kyung commentedon May 19, 2026
@fengmk2 Thanks for the clarification. I’ll open a revert PR for #1540.
revert: remove vp pm plugin command (#1623)
release: v0.1.22 (#1637)