vp why -g and vp outdated -g should check global packages managed by Vite+

Describe the bug

Ideally, all global pm commands in Vite+ like vp outdated -g, vp update -g, vp install -g, vp uninstall -g should be used to control packages inside ~/.vite-plus/packages.

However, vp outdated -g and vp why -g here just delegate the command to npm with a --global field, makes it show packages managed by the corresponding pm, not Vite+'s global packages.

It needs Vite+ to implement vp outdated -g and vp why -g here.

Reproduction

https://github.com/liang-demos/vp-global-outdated.git

Steps to reproduce

vp outdated -g

Validations

Read the Contributing Guidelines.
Check that there isn't already an issue for the same bug.
Confirm this is a Vite+ issue and not an upstream issue (Vite, Vitest, tsdown, Rolldown, or Oxc).
The provided reproduction is a minimal reproducible example.

@liangmiQwQ

@liangmiQwQ Are you willing to continue fixing such problems?

Yeah

@fengmk2

vp outdated -g is implemented in #1659.

However, I am a little hesitate about whether to add vp why -g. Semantically speaking, Vite+'s global packages are isolated under $VP_HOME/packages, means they won't share dependency graph. why normally explains why a dependency exists in a workspace or shared structure.

What's more, I found that npm itself does not support global why commands, and neither does yarn. This can help reflect why -g doesn't seem to have much meaning. The missing npm why -g also makes implementation more difficult (we have to direct to package's node_module and let npm to analyze it as a workspace, then merge and modify npm's result into a big json and finally print it in a certain struct.)

Based on that, I personally would prefer just remove vp why -g, or add a unsupported flag.

What do you think of it? @fengmk2

feat(cli): check managed global outdated packages (#1659)

feat(cli): check managed global outdated packages (voidzero-dev#1659)

@fengmk2

vp outdated -g is implemented in #1659.

However, I am a little hesitate about whether to add vp why -g. Semantically speaking, Vite+'s global packages are isolated under $VP_HOME/packages, means they won't share dependency graph. why normally explains why a dependency exists in a workspace or shared structure.

What's more, I found that npm itself does not support global why commands, and neither does yarn. This can help reflect why -g doesn't seem to have much meaning. The missing npm why -g also makes implementation more difficult (we have to direct to package's node_module and let npm to analyze it as a workspace, then merge and modify npm's result into a big json and finally print it in a certain struct.)

Based on that, I personally would prefer just remove vp why -g, or add a unsupported flag.

What do you think of it? @fengmk2

@fengmk2 Sorry for pinging, but please take a look there when you are free, thanks a lot.

@liangmiQwQ

@liangmiQwQ Agreed, vp why doesn't need to support the -g flag.

fix(cli): remove global why flag (#1720)

Navigation Menu

Repository navigation

`vp why -g` and `vp outdated -g` should check global packages managed by Vite+ #1656

Describe the bug

Reproduction

Steps to reproduce

Validations

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

vp why -g and vp outdated -g should check global packages managed by Vite+ #1656

Description

Describe the bug

Reproduction

Steps to reproduce

Validations

Activity

fengmk2 commented on May 21, 2026

liangmiQwQ commented on May 21, 2026

liangmiQwQ commented on May 23, 2026

liangmiQwQ commented on May 30, 2026

fengmk2 commented on May 30, 2026

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions

`vp why -g` and `vp outdated -g` should check global packages managed by Vite+ #1656