Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Make global packages always available

Open
#13 4 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
nodejs
Domain
cli, tooling

Research direction

The issue describes npm global packages disappearing after vfox use switches Node.js versions, but names no files, tests, or entry points. Start by locating the vfox-nodejs handling for npm install -g and version switching; done would mean a globally installed command remains available and runs with the Node.js version where it was installed.

Written by the indexing model from the issue text.

Description

enhancement help wanted

A very nice feature would be to make global packages are always available, like with Volta.

Current behavior

  1. Run npm install -g rimraf with a NodeJS managed by vfox
  2. The rimraf command is available
  3. Run vfox use to a different NodeJS version
  4. The rimraf command isn't found anymore

Expected behavior

  1. Run npm install -g rimraf with a NodeJS managed by vfox
  2. The rimraf command is available
  3. Run vfox use to a different NodeJS version
  4. The `rimraf command is available and it is ran by the NodeJS version on which it was installed.

I guess it may need some major changes to vfox core but it could also benefit other platforms, like Bun, Deno and Python pip packages.

Dominant language
Lua
Stars
9
Forks
8
Avg merge
1m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.