Installation: Fails to install and thinks it installed successfully

[babakfp]

Describe the bug

This issue is only about installation.

PowerShell 7.6.3
PS C:\Users\Babak> irm https://vite.plus/ps1 | iex

Setting up VITE+...

✔ VITE+ successfully installed!

  The Unified Toolchain for the Web.

  Get started:
    vp create       Create a new project
    vp env          Manage Node.js versions
    vp install      Install dependencies
    vp migrate      Migrate to Vite+

  Vite+ is now managing Node.js via vp env.
  Run vp env doctor to verify your setup, or vp env off to opt out.

  Run vp help to see available commands.

  Shell configuration:
    - Windows PATH: updated

  Note: Restart your terminal and IDE for changes to take effect.

Using vp command after this did not work. Restarting terminal did nothing. Restarting PC did nothing. There was no .vite-plus folder in Home (C:\Users\Babak).

After restarting I have PowerShell elevation to administration and after a long time (probably internet issues) it installed.

It's important to note that there was no errors or requests for administration elevation.

I'm not sure if elevation was the issue, so it would need some investigation.

Another thing to keep it mind is my 💩 internet. But if internet is bad, I don't get why it would think it installed successfully.

Reproduction

.

Steps to reproduce

No response

System Info

Windows 11


PS C:\Users\Babak> vp env current
VITE+ - The Unified Toolchain for the Web

Environment:
  Version  24.18.0
  Source   lts

Tool Paths:
  node  C:\Users\Babak\.vite-plus\js_runtime\node\24.18.0\node.exe
  npm   C:\Users\Babak\.vite-plus\js_runtime\node\24.18.0\npm.cmd
  npx   C:\Users\Babak\.vite-plus\js_runtime\node\24.18.0\npx.cmd

PS C:\Users\Babak> vp --version
VITE+ - The Unified Toolchain for the Web

vp v0.2.4

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          v24.18.0

Used Package Manager

npm

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.

[bulebrainbrand]

I have a little related experienced it once too. in my case (windows11), when i run vp's command, It takes long time(a minute) to start running. there are workspace vp and global vp, vp version is 2.1.0 . then i upgrade global vp and it is not reproduction.

[liangmiQwQ]

I guess there is a Windows-specific bug in the install script, that ignores a step's failure and makes this happens.

This is a little bit hard to reproduce, however, because it sounds strange and tests seems to work fine.

I guess maybe it is caused by mklink failure, that creates junction and its exitcode is ignore. But I think that more investigation and clues are helpful here :)