Repository navigation
Support Yarn plugin commands in vp pm #1539
Description
Describe the feature
vp pm is not currently a full replacement for invoking package managers directly in all cases.
A concrete gap called out in #1309 is support for yarn plugin ... commands. Right now, one reason users still need access to the actual yarn binary is that these plugin-management commands are not available through vp pm.
If the long-term direction is for Vite+ shims or package-manager commands to replace direct yarn/pnpm usage, vp pm needs to cover these workflows too.
Motivation
This came up in the discussion on #1309:
vp pmdoesn't support theyarn plugin ...commands, so it's not a full replacement to having access to the correct version ofyarnfor instance.
Without this support, adding shims alone may still leave gaps for users who rely on Yarn plugin commands.
Suggested direction
- Add support for
yarn plugin ...commands viavp pm - Or document the intended alternative if these commands are intentionally out of scope
Reproduction
- Use a project/workflow that relies on
yarn plugin ... - Try to perform the same action through
vp pm - Observe that the workflow is not currently supported
Metadata
Metadata
Assignees
Type
Fields
Priority
Activity
rChaoz commentedon May 9, 2026
If
vite-plusis to shim PMs in the future, I think it's worth noting that it should maybe bypass unknown commands automatically.If
yarnever adds ayarn whatevercommand, I expectvp pm whateverto simply callyarndirectly, without doing anything else. Is there an issue with this approach?jong-kyung commentedon May 9, 2026
@rChaoz Same tension I've been wrestling with.
I was planning explicit mapping —
vp pm yarn-plugin <sub>wrapping each yarn plugin command, consistent withOwner/Token/DistTag. Yarn 2+ dispatches; other PMs warn and exit 0.But that makes it the first
PmCommandsvariant where 4 of 5 PMs only print a warning.@fengmk2 — should
vp pmcarry single-PM-only commands, or isyarn pluginbetter left out of scope?fengmk2 commentedon May 9, 2026
According to the current design, it will be placed under
vp pm plugin, and will only take effect under yarn. In pnpm and npm, warning messages will be printed as a reminder, which can refer to the existing pm subcommands.feat(cli): support yarn plugin commands via vp pm plugin (#1540)