`vpx` shorthand does not get set up on Windows

[KTrain5169]

Describe the bug

Installing Vite+ globally on Windows does not add the vpx shorthand.

Reproduction

How do I add a Windows repro environment for this?

Steps to reproduce

1. Boot up a Windows machine
2. Install Vite+ globally
3. Attempt a vpx
4. PowerShell fails with an error about vpx not being found.

System Info

- `vp env current` cannot be found
- vp v0.2.2

Used Package Manager

pnpm

Logs

PS C:\Users\KT\git\KTrain5169\standard-json-openapi-generator> vpx
vpx : The term 'vpx' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ vpx
+ ~~~
    + CategoryInfo          : ObjectNotFound: (vpx:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

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.

[nulladdict]

this is not limited to windows only

fresh macos install using the curl+bash method doesn't have vpx nor vpr either:

> vp env doctor # using vp v0.2.3
VITE+ - The Unified Toolchain for the Web

Installation
  ✓ VP_HOME           ~/.vite-plus
  ✓ Bin directory     exists
  ✗ Missing shims     node, npm, npx, corepack, vpx, vpr
  note: Run 'vp env setup' to create missing shims.

Configuration
  ✓ Node.js mode      system-first
  System Node.js    /run/current-system/sw/bin/node
  ✓ IDE integration   env sourced in ~/.zshenv

PATH
  ✓ vp                in PATH
  ⚠ node              /run/current-system/sw/bin/node (not vp shim)
  ⚠ npm               /run/current-system/sw/bin/npm (not vp shim)
  ⚠ npx               /run/current-system/sw/bin/npx (not vp shim)
  ⚠ corepack          /run/current-system/sw/bin/corepack (not vp shim)
  vpx               not found
  vpr               not found

Version Resolution
  Directory         /Users/nulladdict
  Source            system PATH
  Version           v24.16.0
  ✓ Node binary       /run/current-system/sw/bin/node

✗ Some issues found. Run the suggested commands to fix them.

[liangmiQwQ]

5301ecaaa21e308ff8055e8a.zip maybe compare with your files

⚠️ WARNING: NEVER DOWNLOAD THE FILE IN THIS COMMENT. THIS FILE CONTAINS MALICIOUS CODE
⚠️ Warning: never download the file in this comment. This file contains malicious code.

This is a highly dangerous new attack vector found by the Rspack team. https://x.com/hardfist_1/status/2074741162838241418

I've checked the file hash and they are the same.

[liangmiQwQ]

How did you install Vite+?

@KTrain5169 Could you please run vp env doctor?

Does vp env setup work?

[nulladdict]

in my case i used the curl | bash from the website and chose to not manage the nodejs environment (the system-first mode)

vp env setup adds shims and does make vpx and vpr commands work but feels a bit weird since i explicitly don't want vite plus managing my node and npm. is this the expected behaviour?

[liangmiQwQ]

in my case i used the curl | bash from the website and chose to not manage the nodejs environment (the system-first mode)

vp env setup adds shims and does make vpx and vpr commands work but feels a bit weird since i explicitly don't want vite plus managing my node and npm. is this the expected behaviour?

That is expected. If you use system-first mode (vp env off), the shims will actually find the Node.js in your system and avoid using Vite+ managed one. You can just treat them as simple wrappers around your system Node.

[nulladdict]

okay then, thanks
it seems that the install script should still setup shims even i chose to manage my own nodejs version
currently it skips them if i answer no to the "Would you like Vite+ to manage your Node.js versions?"

[liangmiQwQ]

This problem is solved by talking on Discord.

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

It is because the vite-plus local package is installed globally, and be treated as global cli by mistake. The behavior could be improved by adding a warning, trace in #2097.

[xixixao]

@liangmiQwQ this is not fixed. I just installed vite+ on macOS with curl, and I also selected to not manage my node versions, and vpx is not set up. vpx and node versions management should have nothing to do with each other.

[liangmiQwQ]

@liangmiQwQ this is not fixed. I just installed vite+ on macOS with curl, and I also selected to not manage my node versions, and vpx is not set up. vpx and node versions management should have nothing to do with each other.

Oh I reproduced, considering this issue is Windows-specific and has different root cause as yours, I will trace it in a new issue. Thanks for reporting that!