Make global packages always available #13

Activity

1. linghengqian commented on Mar 19, 2025

   

   linghengqian

   on Mar 19, 2025

   Member

   More actions

   • This sounds strange, but in contrast, nodejs version managers like https://github.com/nvm-sh/nvm actively reject this design. nvm always installs global packages to the latest version nvm-sh/nvm#2011 (comment) explains why this causes PATH conflicts.
2. rcsilva83 commented on Mar 19, 2025

   

   rcsilva83

   on Mar 19, 2025

   Author

   More actions

   Hi @linghengqian. The comment you mentioned doesn't sound a "rejection" of the proposed design to me. The person only describes how nvm works.

   I'm happy with Volta but I need version managers for other languages (Java mainly). If I could stick with a single tool (vfox) for all my "tool version management" needs would be great :)
3. danreeves commented on Jul 30, 2025

   

   danreeves

   on Jul 30, 2025

   More actions

   asdf-nodejs has a .default-npm-packages feature which handles this nicely https://github.com/asdf-vm/asdf-nodejs#default-npm-packages. I usually don't want every package I install globally to follow me around but it's nice to have an opt-in list of my commonly used tools
4. linghengqian commented on Sep 21, 2026

   

   linghengqian

   on Sep 21, 2026

   Member

   More actions

   • From my perspective, this issue is a bit odd, given that pnpm has essentially superseded tools like nvm, Volta, and even vfox. pnpm can now manage dependencies for cargo, PyPI, and npm simultaneously, while also handling version management for Node.js, Bun, and Deno.
   • This makes conflicts quite likely from vfox's standpoint.
5. linghengqian

   added

   enhancementNew feature or requestNew feature or request

   help wantedExtra attention is neededExtra attention is needed

   on Sep 21, 2026
6. linghengqian commented on Oct 12, 2026

   

   linghengqian

   on Oct 12, 2026

   Member

   More actions

   • I have the impression that this issue has actually already been resolved by pnpm. It makes no sense to address this issue from the perspective of Node.js, as Node.js is not a package manager.
   • For example, if you execute,

   vfox add nodejs
   vfox install nodejs@26.10.0
   sudo apt install --assume-yes libatomic1
   vfox use --global nodejs@26.10.0
   npm install --global npm@latest
   npx --yes get-pnpm
   source ~/.bashrc
   pnpm add --global @playwright/cli@latest

   • At this point, if you run which playwright-cli, you will find that the installation location of @playwright/cli@latest is completely independent of the Node.js version; no matter which Node.js version you switch to, the global package installed via pnpm remains available.

   lingh@DESKTOP-7B05G9H:~/TwinklingLiftWorks/git/public$ which playwright-cli
   /home/lingh/.local/share/pnpm/bin/playwright-cli
   lingh@DESKTOP-7B05G9H:~/TwinklingLiftWorks/git/public$

   • If there is no response, I will close this issue in a month.
7. linghengqian

   added

   invalidThis doesn't seem rightThis doesn't seem right

   questionFurther information is requestedFurther information is requested

   and removed

   enhancementNew feature or requestNew feature or request

   help wantedExtra attention is neededExtra attention is needed

   invalidThis doesn't seem rightThis doesn't seem right

   on Oct 12, 2026