Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#2,984 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
30/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
powershell
Ambito
developer-experience

Direzione di ricerca

Start with install.ps1 and the Invoke-InstallHandoff step, then find the self-setup code that reads state\self-setup\*.json and writes the user PATH (HKCU\Environment\Path). Check whether the write is skipped or fails silently, including with a REG_EXPAND_SZ PATH containing %PNPM_HOME% and empty entries. Done means a fresh install on Windows leaves %LOCALAPPDATA%\vite-plus\bin in the user PATH so vp resolves in a new PowerShell session.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
  1. On Windows 11 Pro (build 26200), in PowerShell 7.1.4, run: irm https://vite.plus/ps1 | iex
  2. Open a new PowerShell window.
  3. Run vp help or vp env doctor. Result: "The term 'vp' is not recognized…"
  4. 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)

Lingua principale
Rust
Stelle
6k
Fork
274
Merge medio
1g 11h
PR unite (30g)
206

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di voidzero-dev/vite-plus

Tutte le issue di voidzero-dev/vite-plus

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.