Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

`npm install -g` keeps the `bin` link on the old version after the default Node.js changes

Aberta
  • Algo errado?
#3,279 1 comentário 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@mondaychen já está trabalhando nisso.

Desde 29/10/2026.

  • #3283 de @mondaychen — aberto

Avaliação

Esta issue ainda não foi avaliada.

Descrição

bug triage: failed
Describe the bug

When Vite+ manages Node.js, npm install -g <pkg> installs the package into the prefix of the active Node.js version. Vite+ then links the package binary into ~/.vite-plus/bin/ and records the owner in ~/.vite-plus/bins/<bin>.json.

When the active Node.js version changes (for example, the latest LTS moves from 24 to 26), I run npm install -g <pkg> again to update the package. npm installs a new copy into the new Node.js prefix and reports success. But the link in ~/.vite-plus/bin/ still points to the copy in the old Node.js prefix. Vite+ shows no message. When I run the command, I get the old version.

Expected: the link points to the copy that npm just installed, or Vite+ tells me that it kept the old link.

Cause: in check_npm_global_install_result, Vite+ replaces an existing link only when a different npm package owns it. When the same package owns it, Vite+ skips it, and it does not compare the link target with the new npm bin directory:

https://github.com/voidzero-dev/vite-plus/blob/7073d613af772874a07f085aa676160131291c57/crates/vp_global_cli/src/shim/dispatch.rs#L287-L313

Possible fix: also replace the link when the same package owns it but the link target is not in the current npm bin directory. Write the new nodeVersion to the bin config, and print a line such as Relinked 'agent-browser' to Node.js 26.13.0 (was 24.15.0).

I can submit a PR for this fix.

Related: #1986 (general discussion about npm install -g and Node.js version management).

Reproduction

No repository is necessary. This is global CLI behavior. See the steps below.

Steps to reproduce
# 1. Install a package with an older default Node.js version
vp env default 24
npm install -g cowsay          # Answer "Y" to create the link
ls -l ~/.vite-plus/bin/cowsay  # -> .../js_runtime/node/24.x.y/bin/cowsay

# 2. Change the default Node.js version, then install the package again
vp env default 26
npm install -g cowsay          # npm reports success; Vite+ prints nothing
ls -l ~/.vite-plus/bin/cowsay  # Still -> .../node/24.x.y/bin/cowsay
cat ~/.vite-plus/bins/cowsay.json   # "nodeVersion" is still 24.x.y

# The new copy exists, but the link does not use it
ls ~/.vite-plus/js_runtime/node/26.*/lib/node_modules/cowsay

Workaround: remove the link (rm ~/.vite-plus/bin/cowsay), then run npm install -g cowsay again; or run vp install -g instead of npm install -g.

On my machine, 7 links point to old Node.js versions (24.15.0, 24.18.0, 24.21.0), while the active version is 26.13.0.

System Info
$ vp env current
Environment:
  Version  26.13.0
  Source   lts

Tool Paths:
  node  /Users/user/.vite-plus/js_runtime/node/26.13.0/bin/node
  npm   /Users/user/.vite-plus/js_runtime/node/26.13.0/bin/npm
  npx   /Users/user/.vite-plus/js_runtime/node/26.13.0/bin/npx

$ vp --version
vp v0.2.1

Local vite-plus:
  vite-plus  Not found

Environment:
  Package manager  Not found
  Node.js          v26.13.0

macOS, npm 10.9.9. The code at the link above is from current main (7073d613), so the bug is also on main.

Used Package Manager

npm

Linguagem predominante
Rust
Estrelas
6.5k
Forks
296
Merge médio
1d 2h
PRs com merge (30d)
230

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de voidzero-dev/vite-plus

Todas as issues de voidzero-dev/vite-plus

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.