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 pm doesn't support the yarn plugin ... commands, so it's not a full replacement to having access to the correct version of yarn for 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 via vp 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
Describe the feature
vp pmis 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 actualyarnbinary is that these plugin-management commands are not available throughvp pm.If the long-term direction is for Vite+ shims or package-manager commands to replace direct
yarn/pnpmusage,vp pmneeds to cover these workflows too.Motivation
This came up in the discussion on #1309:
Without this support, adding shims alone may still leave gaps for users who rely on Yarn plugin commands.
Suggested direction
yarn plugin ...commands viavp pmReproduction
yarn plugin ...vp pm