Windows PATH issue, 'vp' not recognized after console restart on fresh install

[Saeris]

Describe the bug

Hey! I had vite+ working on the first time I installed it, and all seemed great. Then I restarted VSCode and now I'm getting a PATH error and I'm not understanding why. I've verified that it is in my system environment variables (see screenshot) so this isn't making any sense to me.

Here's the console output I get after running the install command again. You can see that immediately calling vp help after the install completes without error that the command can't be run.

PS C:\GitHub\@saeris\saeris.gg> 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.

PS C:\GitHub\@saeris\angel-attack> vp help
vp : The term 'vp' 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
+ vp help
+ ~~
    + CategoryInfo          : ObjectNotFound: (vp:String) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : CommandNotFoundException

PS C:\GitHub\@saeris\saeris.gg>

It will however work when I run the command using a package manager such as yarn in a repository where vite+ is included as a dependency:

PS C:\GitHub\@saeris\saeris.gg> yarn vp --version  
VITE+ - The Unified Toolchain for the Web

vp v0.1.11

Local vite-plus:
  vite-plus  v0.1.11

Tools:
  vite             v8.0.0
  rolldown         v1.0.0-rc.9
  vitest           v4.1.0
  oxfmt            v0.40.0
  oxlint           v1.55.0
  oxlint-tsgolint  v0.16.0
  tsdown           v0.21.2

(I tried running vp env --current as requested in the issue template, but I got a command not found error there too)

I'll restart my machine again and see if the issue goes away on its own. I'm doubtful that it has anything to do with me having used volta to install node/yarn and the like, but I thought I'd mention it because I see that vite+ also manages node.

Reproduction

N/A

Steps to reproduce

Fresh install of vite plus on Windows inside PowerShell in VSCode's terminal using:

irm https://vite.plus/ps1 | iex

Restart VSCode

Attempt to run any vp command, such as vp help

System Info

VITE+ - The Unified Toolchain for the Web

vp v0.1.11

Local vite-plus:
  vite-plus  v0.1.11

Tools:
  vite             v8.0.0
  rolldown         v1.0.0-rc.9
  vitest           v4.1.0
  oxfmt            v0.40.0
  oxlint           v1.55.0
  oxlint-tsgolint  v0.16.0
  tsdown           v0.21.2

Used Package Manager

yarn

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.

[jjuker]

I have resolved this issue by upgrading to version 0.1.12
you can try vp upgrade