Windows: PowerShell installer (1.1.0) does not add vite-plus\bin to user PATH — 'vp' not recognized
Mantenedores costumam responder em até 1 dia
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 30/100
- Tipo de issue
- Bug
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- powershell
- Domínio
- developer-experience
Direção de pesquisa
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.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
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 helporvp 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)
- Linguagem predominante
- Rust
- Estrelas
- 6.5k
- Forks
- 297
- Merge médio
- 1d 2h
- PRs com merge (30d)
- 247
Preparar o ambiente
Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.
- Sem Dockerfile nem arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de voidzero-dev/vite-plus
-
triage: not actionable
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 85/100
voidzero-dev/vite-plus#3296 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
pending triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 63/100
voidzero-dev/vite-plus#3235 ·
Mantenedores costumam responder em até 1 dia
-
Docker guide: the runtime stage needs libatomic1 for Node.js 25 and laterTalvez já em andamento @kshanxs assumiu há 10 dias. Abertadocumentation
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 84/100
voidzero-dev/vite-plus#3219 · 2 comentários · 1 reação ·
Mantenedores costumam responder em até 1 dia
-
pending triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
voidzero-dev/vite-plus#2882 · 2 comentários ·
Mantenedores costumam responder em até 1 dia
-
Yarn command gates use the launcher version instead of the version selected by yarnPathTalvez já em andamento @jong-kyung assumiu hoje. Aberta- P2: has workaround
voidzero-dev/vite-plus#3327 · 1 responsável ·
Mantenedores costumam responder em até 1 dia
Todas as issues de voidzero-dev/vite-plus
Issues semelhantes
-
A-linter
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 73/100
oxc-project/oxc#28783 ·
Mantenedores costumam responder em até 1 dia
-
Substrait consumer doesn't recognise `shift_left` / `shift_right` from functions_arithmetic.yamlAbertabug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
apache/datafusion#27059 ·
Mantenedores costumam responder em até 1 dia
-
Bump calamine to 0.38: RUSTSEC-2026-0436 (CFB/OLE2 panic and unbounded allocation) fails cargo auditAberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
docling-project/docling.rs#979 ·
Mantenedores costumam responder em até 1 dia
-
llm translation
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
Mantenedores costumam responder em até 1 dia