Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

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

未关闭
#2,984 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@fengmk2 已经在做这个了。

开始于 2026年10月12日。

  • #3012 来自 @fengmk2 —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
powershell

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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)

主要语言
Rust
星标
6k
派生
274
平均合并
1 天 11 小时
30 天内合并 PR
196

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

voidzero-dev/vite-plus 的其他 Issue

查看 voidzero-dev/vite-plus 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。