Forward various commands using `vp pm`

[thinceller]

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

• https://pnpm.io/cli/deploy

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.

[cpojer]

We don't support every single package manager command as we aim to provide a common interface across all package managers. deploy is implemented by some, but not by all.

If you rely on pnpm's deploy command, I suggest defining a deploy script that does pnpm deploy. Then you can use vp run deploy.

[thinceller]

If you rely on pnpm's deploy command, I suggest defining a deploy script that does pnpm deploy. Then you can use vp run deploy.

This workaround seems like it will work well.
Thank you for the response.

[thinceller]

@cpojer By the way, the documentation for the vp pm command states the following:

vite-plus/docs/guide/install.md

Line 122 in d62e5d9

- `vp pm <command>` forwards directly to the resolved package manager

As you explained, vp pm provides 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 that vp pm deploy would work.

Would it be worth updating the documentation to more accurately describe what vp pm does?

[cpojer]

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]

@cpojer I firmly believe this feature is necessary.

We don't support every single package manager command as we aim to provide a common interface across all package managers. deploy is implemented by some, but not by all.

But in fact, version v0.1.21 introduced a dedicated vp pm plugin subcommand specifically for yarn, which actually contradicts what you said about "provide a common interface across all package managers." Since a special case has already been created for yarn, should special cases also be created for npm x, pnpm y, and bun 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:

• For the command vp pm <cmd> [options], first check if cmd is a known command
• If so, then process according to the current logic
• If not, then transparently forward cmd and options to the package manager under the hood, whether cmd and options are valid should be confirmed by the user themselves

[fengmk2]

We don't support every single package manager command as we aim to provide a common interface across all package managers.

@jong-kyung vp pm plugin broke this rule, we need to revert #1540

[jong-kyung]

@fengmk2 Thanks for the clarification. I’ll open a revert PR for #1540.