Vite-plus global bin installs doesn't store version range metadata

[BlankParticle]

Describe the bug

when installing a package globally with @version, it doesn't store the range metadata
which means when running vp up later, it installs the latest version instead of specified tag

context https://discord.com/channels/1475973262193459293/1530588150693494815

Reproduction

https://discord.com/channels/1475973262193459293/1530588150693494815

Steps to reproduce

1. Install a package with a non-latest tag, vp i react@next -g as example
2. Run vp up -g
3. See a stable version of react got installed replacing the next version

System Info

Environment:
  Version      25.9.0
  Source       default
  Source Path  /home/blank/.vite-plus/config.json

Tool Paths:
  node  /home/blank/.vite-plus/js_runtime/node/25.9.0/bin/node
  npm   /home/blank/.vite-plus/js_runtime/node/25.9.0/bin/npm
  npx   /home/blank/.vite-plus/js_runtime/node/25.9.0/bin/npx


vp v0.2.6

Local vite-plus:
  vite-plus  Not found

Tools:
  vite             Not found
  rolldown         Not found
  vitest           Not found
  oxfmt            Not found
  oxlint           Not found
  oxlint-tsgolint  Not found
  tsdown           Not found

Environment:
  Package manager  Not found
  Node.js          v25.9.0

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.

[TheAlexLichter]

Note that the current behavior is in line with how npm handles globals but is not the most desired option. Here are what other package manager do:

• pnpm keeps the exact resolved version and never touches it (not even with pnpm update -g --latest
• yarn and bun do update to another fitting version (within range), but alphabetically and not by build date order.

Each of them has caveats:

• npm fails because it just downgrades to latest
• pnpm fails by no-opping for tag installs
• yarn/bun fail because they could install older version instead

Thus, I am considering neither (but close to yarn/bun) and propose this behavior:

• tag -> use newest of that tag
• range -> use newest in range
• pin -> that exact version
• nothing -> use latest

[BlankParticle]

I like this behaviour, vite-plus should take opportunity to improve the global installation version issue, like it did with coupling node versions with packages, which made it my fav way to do global installs

one feature to add here is --latest to install all latest versions like other package managers too

[TheAlexLichter]

one feature to add here is --latest to install all latest versions like other package managers too

That could be a nice iteration on top of it 👍🏻