Windows: PowerShell installer (1.1.0) does not add vite-plus\bin to user PATH — 'vp' not recognized

Describe the bug

On Windows 11, installing Vite+ with the PowerShell installer completes, but the bin directory (%LOCALAPPDATA%\vite-plus\bin) is never added to the user PATH. In a new PowerShell session, vp is not found:

vp: The term 'vp' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

What I expect: after the installer finishes (and a new terminal is opened), vp resolves from PATH.

What actually happens: the install itself is fine. Every file is in place, state\self-setup\*.json was written, and running vp.exe by its full path works. But the user PATH (HKCU\Environment\Path) has no vite-plus entry. As far as I can tell from install.ps1, the PATH update is delegated to the vp self-setup handoff (Invoke-InstallHandoff); that step apparently ran but never persisted the user PATH change.

This looks similar to #973, but that was on 0.1.x and was fixed by upgrading. This is a fresh install of 1.1.0.

Reproduction

N/A. No project needed; this is a global install issue (steps below).

Steps to reproduce

On Windows 11 Pro (build 26200), in PowerShell 7.1.4, run: irm https://vite.plus/ps1 | iex
Open a new PowerShell window.
Run vp help or vp env doctor. Result: "The term 'vp' is not recognized…"
Run & "$env:LOCALAPPDATA\vite-plus\bin\vp.exe" env doctor. It works and reports the PATH problem:

PATH
  ✗ vp                not in PATH
  note: Run 'vp env setup' to create the vp shim.
  ✗ Shim dir          not in PATH
  note: Expected: C:\Users\<user>\AppData\Local\vite-plus\bin

(All Installation and Configuration checks pass, including shims.)

Possibly relevant: my existing user PATH is a REG_EXPAND_SZ value that contains an unexpanded variable entry (%PNPM_HOME%) and one empty entry (;;). Total length is about 817 characters. I haven't confirmed whether either of these affects the self-setup PATH write.

Workaround: manually prepend %LOCALAPPDATA%\vite-plus\bin to the user PATH and restart the terminal.

System Info

> vp env current
Node.js:
  Version    24.21.0
  Source     lts
  Bin Path   C:\Users\<user>\AppData\Local\vite-plus\data\js_runtime\node\24.21.0\node.exe
  Installed  true
  Mode       managed

> vp --version
vp v1.1.0

OS: Windows 11 Pro 10.0.26200
Shell: PowerShell 7.1.4

Used Package Manager

N/A (global install; no package manager selected yet)

Follow-up: the manual workaround worked, with one extra step.

Prepending only %LOCALAPPDATA%\vite-plus\bin to the user PATH fixed vp itself. However, vp env doctor then reported a second missing entry:

PATH
  ✓ vp                C:\Users\<user>\AppData\Local\vite-plus\bin\vp.exe
  ✓ Shim dir          C:\Users\<user>\AppData\Local\vite-plus\bin
  ✗ Fallback dir      not in PATH

So the self-setup wrote neither PATH entry, bin (front) or data\fallback-bin (end). Also, the doctor message for the fallback dir doesn't say which directory to add. I found the expected layout (bin first, fallback last) in the PowerShell snippet embedded in vp.exe.

After also appending %LOCALAPPDATA%\vite-plus\data\fallback-bin to the end of the user PATH (kept as REG_EXPAND_SZ) and opening a new terminal, vp env doctor reports "All checks passed".

Full workaround for anyone else hitting this:

$bin = "$env:LOCALAPPDATA\vite-plus\bin"
$fb  = "$env:LOCALAPPDATA\vite-plus\data\fallback-bin"
$old = (Get-Item HKCU:\Environment).GetValue('Path', '', 'DoNotExpandEnvironmentNames')
Set-ItemProperty HKCU:\Environment -Name Path -Value "$bin;$old;$fb" -Type ExpandString
# then restart your terminal(s)

chore(deps): update rust crates (#1780)

@dagilleland

@dagilleland #3012 (comment) Could you help verify this using the preview build version and check whether the issue has been fixed?

chore(deps): update npm packages (#3108)

Follow-up: the manual workaround worked, with one extra step.
Prepending only %LOCALAPPDATA%\vite-plus\bin to the user PATH fixed vp itself. However, vp env doctor then reported a second missing entry:
PATH
  ✓ vp                C:\Users\<user>\AppData\Local\vite-plus\bin\vp.exe
  ✓ Shim dir          C:\Users\<user>\AppData\Local\vite-plus\bin
  ✗ Fallback dir      not in PATH

I had the same error, but in my case even after that error, when I checked my environment variables, I saw that the fallback-bin was actually there, only the vite-plus\bin was not there and had to add it myself. I only had to open a new terminal and then run vp env doctor and saw that the error was no longer showing.

That being said, even though I can access vp commands from any powershell/cmd now, I still get the error in VSCode:

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) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Maybe I have to configure VSCode as well? But I ran VSCode after installing Vite Plus, so it should get the env variables...

Maybe I have to configure VSCode as well? But I ran VSCode after installing Vite Plus, so it should get the env variables...

Oh, managed to fix that. I was following the guide on vite-plus
But I should've followed the CLI's "Next Step" instead when installing vite-plus.
After creating a $PROFILE
and then ". '...\Roaming\vite-plus\env.ps1'", VSCode now has access to vp commands as well.

Navigation Menu

Windows: PowerShell installer (1.1.0) does not add vite-plus\bin to user PATH — 'vp' not recognized #2984

Describe the bug

Reproduction

Steps to reproduce

System Info

Used Package Manager

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Windows: PowerShell installer (1.1.0) does not add vite-plus\bin to user PATH — 'vp' not recognized #2984

Description

Describe the bug

Reproduction

Steps to reproduce

System Info

Used Package Manager

Activity

dagilleland commented on Oct 10, 2026

fengmk2 commented on Oct 16, 2026

Rahat47313 commented on Oct 20, 2026

Rahat47313 commented on Oct 20, 2026

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions