`vp upgrade` + `vp update vite-plus` doesn't update the `@voidzero-dev/vite-plus-core` alias

[gradyat]

Describe the bug

After running the two upgrade commands from the Upgrade guide (vp upgrade and vp update vite-plus), vp outdated still reports @voidzero-dev/vite-plus-core as outdated.

The "vite": "npm:@voidzero-dev/vite-plus-core@latest" alias (and the corresponding overrides) is set up as part of the standard vite-plus installation, but neither upgrade command re-resolves it in the lockfile. Users need to manually run vp update @voidzero-dev/vite-plus-core to fully upgrade, which isn't documented and requires knowledge of this package name.

Reproduction

N/A — reproducible in any project using the standard vite-plus setup with the vite alias.

Steps to reproduce

1. Have a project set up per the vite-plus getting started guide, with "vite": "npm:@voidzero-dev/vite-plus-core@latest" in package.json and corresponding overrides
2. Wait for a new vite-plus release (e.g., 0.1.14 → 0.1.15)
3. Run vp upgrade
4. Run vp update vite-plus
5. Run vp outdated
6. @voidzero-dev/vite-plus-core is still listed as outdated
7. Must manually run vp update @voidzero-dev/vite-plus-core to resolve

System Info

VITE+ - The Unified Toolchain for the Web

Environment:
  Version       24.14.1
  Source        .node-version
  Source Path   C:\Users\Grady\folder\project\.node-version
  Project Root  C:\Users\Grady\folder\project

vp v0.1.15

Local vite-plus:
  vite-plus  v0.1.15

Tools:
  vite             v8.0.3
  rolldown         v1.0.0-rc.12
  vitest           v4.1.2
  oxfmt            v0.43.0
  oxlint           v1.58.0
  oxlint-tsgolint  v0.18.1
  tsdown           v0.21.7

Used Package Manager

pnpm

Logs

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.

[fengmk2]

Let's improve the document description.