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

Vite Plus PATH shim can shadow external CLI upgrades (OpenCode example)

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
50/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
node.js, rust

调研方向

首先使用 opencode --version 和 opencode upgrade --print-logs 复现 Windows PowerShell 案例,然后检查 Vite Plus 如何将可执行文件放置在 ~/.vite-plus/bin 中,以及 PATH 如何解析它们。完成的标准是:外部升级成功后,普通的 opencode 命令能够运行新安装的版本,而无需手动替换;除非确认了其他案例,否则保持围绕 OpenCode 所声明的范围。

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

描述

Summary

On Windows, a Vite Plus-owned executable in ~\.vite-plus\bin can remain ahead of a newer version installed by that CLI's own updater. The shell command then continues to run the stale Vite Plus executable.

OpenCode is the confirmed example below. This may affect any externally updatable CLI for which Vite Plus installs an executable with the same command name, but this report does not claim other packages are currently affected.

Environment

  • Windows
  • Vite Plus: 0.2.4
  • OpenCode before upgrade: 1.17.18

Reproduction

opencode --version
# 1.17.18

opencode upgrade --print-logs

The updater reported:

Using method: npm
From 1.17.18 → 1.18.1
Upgrade complete

But immediately afterwards:

opencode --version
# 1.17.18

Investigation

The command resolved to the Vite Plus-owned path:

C:\Users\<user>\.vite-plus\bin\opencode.exe

The updater had installed OpenCode 1.18.1 at:

C:\Users\<user>\.vite-plus\js_runtime\node\22.19.0\node_modules\opencode-ai\bin\opencode.exe

Running that executable directly returned 1.18.1; the PATH executable remained at 1.17.18.

Scope checked

  • Confirmed: opencode was shadowed by the stale Vite Plus executable.
  • Not implicated in this installation: npm, npx, and corepack resolve to NVM rather than ~\.vite-plus\bin.
  • Potentially affected pattern: any CLI that manages its own upgrades while Vite Plus also places a same-named executable earlier on PATH.

Expected behavior

After a CLI reports a successful self-upgrade, its normal shell command should run the upgraded version.

Workaround

Replacing the stale Vite Plus executable with the newly installed OpenCode executable made opencode --version report 1.18.1.

Suggested direction

Vite Plus could avoid installing static, same-named binaries for externally self-updating CLIs, make them forwarding shims, or provide a way to refresh the Vite Plus bin entry after an external upgrade.

主要语言
Rust
星标
6k
派生
271
平均合并
1 天 12 小时
30 天内合并 PR
198

环境准备

在 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 摘要。