{ "componentChunkName": "component---src-templates-issues-tsx", "path": "/issues/408", "result": {"data":{"issuesJson":{"id":"0ab4c806-662f-58a6-a4b6-7b71115a06a5","title":"nvm-sh/nvm: 一个简单的工具，用于多个 Node 版本的管理与切换","number":408,"bodyHTML":"
\n



\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Reposnvm-sh/nvm
Views\"views\"
Stars\"stars\"
Forks\"forks\"
License\"license\"
UpdatedAt\"last-commit\"
CreatedAt\"create-at\"
\n\n

\"\"

\n\n
\n\n \n \n \"nvm\n \n\n

Node Version Manager \"Build \"nvm \"CII

\n\n\n\n

Table of Contents

\n\n\n

Intro

\n

nvm allows you to quickly install and use different versions of node via the command line.

\n

Example:

\n
$ nvm use 16\nNow using node v16.9.1 (npm v7.21.1)\n$ node -v\nv16.9.1\n$ nvm use 14\nNow using node v14.18.0 (npm v6.14.15)\n$ node -v\nv14.18.0\n$ nvm install 12\nNow using node v12.22.6 (npm v6.14.5)\n$ node -v\nv12.22.6
\n

Simple as that!

\n

About

\n

nvm is a version manager for node.js, designed to be installed per-user, and invoked per-shell. nvm works on any POSIX-compliant shell (sh, dash, ksh, zsh, bash), in particular on these platforms: unix, macOS, and windows WSL.

\n


\n

\n

Installing and Updating

\n

Install & Update Script

\n

To install or update nvm, you should run the install script. To do that, you may either download and run the script manually, or use the following cURL or Wget command:

\n
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash
\n
wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash
\n

Running either of the above commands downloads a script and runs it. The script clones the nvm repository to ~/.nvm, and attempts to add the source lines from the snippet below to the correct profile file (~/.bashrc, ~/.bash_profile, ~/.zshrc, or ~/.profile). If you find the install script is updating the wrong profile file, set the $PROFILE env var to the profile file’s path, and then rerun the installation script.

\n

\n
export NVM_DIR=\"$([ -z \"${XDG_CONFIG_HOME-}\" ] && printf %s \"${HOME}/.nvm\" || printf %s \"${XDG_CONFIG_HOME}/nvm\")\"\n[ -s \"$NVM_DIR/nvm.sh\" ] && \\. \"$NVM_DIR/nvm.sh\" # This loads nvm
\n

Additional Notes

\n\n
export NVM_DIR=\"$([ -z \"${XDG_CONFIG_HOME-}\" ] && printf %s \"${HOME}/.nvm\" || printf %s \"${XDG_CONFIG_HOME}/nvm\")\"\n[ -s \"$NVM_DIR/nvm.sh\" ] && \\. \"$NVM_DIR/nvm.sh\" --no-use # This loads nvm, without auto-using the default version
\n\n

Installing in Docker

\n

When invoking bash as a non-interactive shell, like in a Docker container, none of the regular profile files are sourced. In order to use nvm, node, and npm like normal, you can instead specify the special BASH_ENV variable, which bash sources when invoked non-interactively.

\n
# Use bash for the shell\nSHELL [\"/bin/bash\", \"-o\", \"pipefail\", \"-c\"]\n\n# Create a script file sourced by both interactive and non-interactive bash shells\nENV BASH_ENV /home/user/.bash_env\nRUN touch \"${BASH_ENV}\"\nRUN echo '. \"${BASH_ENV}\"' >> ~/.bashrc\n\n# Download and install nvm\nRUN curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.2/install.sh | PROFILE=\"${BASH_ENV}\" bash\nRUN echo node > .nvmrc\nRUN nvm install
\n
Installing in Docker for CICD-Jobs
\n

More robust, works in CI/CD-Jobs. Can be run in interactive and non-interactive containers.
\nSee nvm-sh/nvm#3531.

\n
FROM ubuntu:latest\nARG NODE_VERSION=20\n\n# install curl\nRUN apt update && apt install curl -y\n\n# install nvm\nRUN curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash\n\n# set env\nENV NVM_DIR=/root/.nvm\n\n# install node\nRUN bash -c \"source $NVM_DIR/nvm.sh && nvm install $NODE_VERSION\"\n\n# set ENTRYPOINT for reloading nvm-environment\nENTRYPOINT [\"bash\", \"-c\", \"source $NVM_DIR/nvm.sh && exec \\\"$@\\\"\", \"--\"]\n\n# set cmd to bash\nCMD [\"/bin/bash\"]\n
\n

This example defaults to installation of nodejs version 20.x.y. Optionally you can easily override the version with docker build args like:

\n
docker build -t nvmimage --build-arg NODE_VERSION=19 .\n
\n

After creation of the image you can start container interactively and run commands, for example:

\n
docker run --rm -it nvmimage\n\nroot@0a6b5a237c14:/# nvm -v\n0.40.3\n\nroot@0a6b5a237c14:/# node -v\nv19.9.0\n\nroot@0a6b5a237c14:/# npm -v\n9.6.3\n
\n

Noninteractive example:

\n
user@host:/tmp/test $ docker run --rm -it nvmimage node -v\nv19.9.0\nuser@host:/tmp/test $ docker run --rm -it nvmimage npm -v\n9.6.3\n
\n

Troubleshooting on Linux

\n

On Linux, after running the install script, if you get nvm: command not found or see no feedback from your terminal after you type command -v nvm, simply close your current terminal, open a new terminal, and try verifying again.
\nAlternatively, you can run the following commands for the different shells on the command line:

\n

bash: source ~/.bashrc

\n

zsh: source ~/.zshrc

\n

ksh: . ~/.profile

\n

These should pick up the nvm command.

\n

Troubleshooting on macOS

\n

Since OS X 10.9, /usr/bin/git has been preset by Xcode command line tools, which means we can't properly detect if Git is installed or not. You need to manually install the Xcode command line tools before running the install script, otherwise, it'll fail. (see #1782)

\n

If you get nvm: command not found after running the install script, one of the following might be the reason:

\n\n

If the above doesn't fix the problem, you may try the following:

\n\n

Note For Macs with the Apple Silicon chip, node started offering arm64 arch Darwin packages since v16.0.0 and experimental arm64 support when compiling from source since v14.17.0. If you are facing issues installing node using nvm, you may want to update to one of those versions or later.

\n

Ansible

\n

You can use a task:

\n
- name: Install nvm\n  ansible.builtin.shell: >\n    curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash\n  args:\n    creates: \"{{ ansible_env.HOME }}/.nvm/nvm.sh\"
\n

Verify Installation

\n

To verify that nvm has been installed, do:

\n
command -v nvm
\n

which should output nvm if the installation was successful. Please note that which nvm will not work, since nvm is a sourced shell function, not an executable binary.

\n

Note: On Linux, after running the install script, if you get nvm: command not found or see no feedback from your terminal after you type command -v nvm, simply close your current terminal, open a new terminal, and try verifying again.

\n

Important Notes

\n

If you're running a system without prepackaged binary available, which means you're going to install node or io.js from its source code, you need to make sure your system has a C++ compiler. For OS X, Xcode will work, for Debian/Ubuntu based GNU/Linux, the build-essential and libssl-dev packages work.

\n

Note: nvm also supports Windows in some cases. It should work through WSL (Windows Subsystem for Linux) depending on the version of WSL. It should also work with GitBash (MSYS) or Cygwin. Otherwise, for Windows, a few alternatives exist, which are neither supported nor developed by us:

\n\n

Note: nvm does not support Fish either (see #303). Alternatives exist, which are neither supported nor developed by us:

\n\n

Note: We still have some problems with FreeBSD, because there is no official pre-built binary for FreeBSD, and building from source may need patches; see the issue ticket:

\n\n

Note: On OS X, if you do not have Xcode installed and you do not wish to download the ~4.3GB file, you can install the Command Line Tools. You can check out this blog post on how to just that:

\n\n

Note: On OS X, if you have/had a \"system\" node installed and want to install modules globally, keep in mind that:

\n\n

Homebrew installation is not supported. If you have issues with homebrew-installed nvm, please brew uninstall it, and install it using the instructions below, before filing an issue.

\n

Note: If you're using zsh you can easily install nvm as a zsh plugin. Install zsh-nvm and run nvm upgrade to upgrade (you can set NVM_AUTO_USE=true to have it automatically detect and use .nvmrc files).

\n

Note: Git versions before v1.7 may face a problem of cloning nvm source from GitHub via https protocol, and there is also different behavior of git before v1.6, and git prior to v1.17.10 can not clone tags, so the minimum required git version is v1.7.10. If you are interested in the problem we mentioned here, please refer to GitHub's HTTPS cloning errors article.

\n

Git Install

\n

If you have git installed (requires git v1.7.10+):

\n
    \n
  1. clone this repo in the root of your user profile\n\n
    2. \n
  2. cd ~/.nvm and check out the latest version with git checkout v0.40.3
    3. \n
  3. activate nvm by sourcing it from your shell: . ./nvm.sh
    4. \n
\n

Now add these lines to your ~/.bashrc, ~/.profile, or ~/.zshrc file to have it automatically sourced upon login:
\n(you may have to add to more than one of the above files)

\n
export NVM_DIR=\"$HOME/.nvm\"\n[ -s \"$NVM_DIR/nvm.sh\" ] && \\. \"$NVM_DIR/nvm.sh\"  # This loads nvm\n[ -s \"$NVM_DIR/bash_completion\" ] && \\. \"$NVM_DIR/bash_completion\"  # This loads nvm bash_completion
\n

Manual Install

\n

For a fully manual install, execute the following lines to first clone the nvm repository into $HOME/.nvm, and then load nvm:

\n
export NVM_DIR=\"$HOME/.nvm\" && (\n  git clone https://github.com/nvm-sh/nvm.git \"$NVM_DIR\"\n  cd \"$NVM_DIR\"\n  git checkout `git describe --abbrev=0 --tags --match \"v[0-9]*\" $(git rev-list --tags --max-count=1)`\n) && \\. \"$NVM_DIR/nvm.sh\"
\n

Now add these lines to your ~/.bashrc, ~/.profile, or ~/.zshrc file to have it automatically sourced upon login:
\n(you may have to add to more than one of the above files)

\n
export NVM_DIR=\"$HOME/.nvm\"\n[ -s \"$NVM_DIR/nvm.sh\" ] && \\. \"$NVM_DIR/nvm.sh\" # This loads nvm\n[ -s \"$NVM_DIR/bash_completion\" ] && \\. \"$NVM_DIR/bash_completion\"  # This loads nvm bash_completion
\n

Manual Upgrade

\n

For manual upgrade with git (requires git v1.7.10+):

\n
    \n
  1. change to the $NVM_DIR
    2. \n
  2. pull down the latest changes
    3. \n
  3. check out the latest version
    4. \n
  4. activate the new version
    5. \n
\n
(\n  cd \"$NVM_DIR\"\n  git fetch --tags origin\n  git checkout `git describe --abbrev=0 --tags --match \"v[0-9]*\" $(git rev-list --tags --max-count=1)`\n) && \\. \"$NVM_DIR/nvm.sh\"
\n

Usage

\n

To download, compile, and install the latest release of node, do this:

\n
nvm install node # \"node\" is an alias for the latest version
\n

To install a specific version of node:

\n
nvm install 14.7.0 # or 16.3.0, 12.22.1, etc
\n

To set an alias:

\n
nvm alias my_alias v14.4.0
\n

Make sure that your alias does not contain any spaces or slashes.

\n

The first version installed becomes the default. New shells will start with the default version of node (e.g., nvm alias default).

\n

You can list available versions using ls-remote:

\n
nvm ls-remote
\n

And then in any new shell just use the installed version:

\n
nvm use node
\n

Or you can just run it:

\n
nvm run node --version
\n

Or, you can run any arbitrary command in a subshell with the desired version of node:

\n
nvm exec 4.2 node --version
\n

You can also get the path to the executable to where it was installed:

\n
nvm which 12.22
\n

In place of a version pointer like \"14.7\" or \"16.3\" or \"12.22.1\", you can use the following special default aliases with nvm install, nvm use, nvm run, nvm exec, nvm which, etc:

\n\n

Long-term Support

\n

Node has a schedule for long-term support (LTS) You can reference LTS versions in aliases and .nvmrc files with the notation lts/* for the latest LTS, and lts/argon for LTS releases from the \"argon\" line, for example. In addition, the following commands support LTS arguments:

\n\n

Any time your local copy of nvm connects to https://nodejs.org, it will re-create the appropriate local aliases for all available LTS lines. These aliases (stored under $NVM_DIR/alias/lts), are managed by nvm, and you should not modify, remove, or create these files - expect your changes to be undone, and expect meddling with these files to cause bugs that will likely not be supported.

\n

To get the latest LTS version of node and migrate your existing installed packages, use

\n
nvm install --reinstall-packages-from=current 'lts/*'
\n

Migrating Global Packages While Installing

\n

If you want to install a new version of Node.js and migrate npm packages from a previous version:

\n
nvm install --reinstall-packages-from=node node
\n

This will first use \"nvm version node\" to identify the current version you're migrating packages from. Then it resolves the new version to install from the remote server and installs it. Lastly, it runs \"nvm reinstall-packages\" to reinstall the npm packages from your prior version of Node to the new one.

\n

You can also install and migrate npm packages from specific versions of Node like this:

\n
nvm install --reinstall-packages-from=5 6\nnvm install --reinstall-packages-from=iojs v4.2
\n

Note that reinstalling packages explicitly does not update the npm version — this is to ensure that npm isn't accidentally upgraded to a broken version for the new node version.

\n

To update npm at the same time add the --latest-npm flag, like this:

\n
nvm install --reinstall-packages-from=default --latest-npm 'lts/*'
\n

or, you can at any time run the following command to get the latest supported npm version on the current node version:

\n
nvm install-latest-npm
\n

If you've already gotten an error to the effect of \"npm does not support Node.js\", you'll need to (1) revert to a previous node version (nvm ls & nvm use <your latest _working_ version from the ls>), (2) delete the newly created node version (nvm uninstall <your _broken_ version of node from the ls>), then (3) rerun your nvm install with the --latest-npm flag.

\n

Default Global Packages From File While Installing

\n

If you have a list of default packages you want installed every time you install a new version, we support that too -- just add the package names, one per line, to the file $NVM_DIR/default-packages. You can add anything npm would accept as a package argument on the command line.

\n
# $NVM_DIR/default-packages\n\nrimraf\nobject-inspect@1.0.2\nstevemao/left-pad
\n

io.js

\n

If you want to install io.js:

\n
nvm install iojs
\n

If you want to install a new version of io.js and migrate npm packages from a previous version:

\n
nvm install --reinstall-packages-from=iojs iojs
\n

The same guidelines mentioned for migrating npm packages in node are applicable to io.js.

\n

System Version of Node

\n

If you want to use the system-installed version of node, you can use the special default alias \"system\":

\n
nvm use system\nnvm run system --version
\n

Listing Versions

\n

If you want to see what versions are installed:

\n
nvm ls
\n

If you want to see what versions are available to install:

\n
nvm ls-remote
\n

Setting Custom Colors

\n

You can set five colors that will be used to display version and alias information. These colors replace the default colors.
\nInitial colors are: g b y r e

\n

Color codes:

\n
r/R = red / bold red\n\ng/G = green / bold green\n\nb/B = blue / bold blue\n\nc/C = cyan / bold cyan\n\nm/M = magenta / bold magenta\n\ny/Y = yellow / bold yellow\n\nk/K = black / bold black\n\ne/W = light grey / white\n
\n
nvm set-colors rgBcm
\n

Persisting custom colors

\n

If you want the custom colors to persist after terminating the shell, export the NVM_COLORS variable in your shell profile. For example, if you want to use cyan, magenta, green, bold red and bold yellow, add the following line:

\n
export NVM_COLORS='cmgRY'
\n

Suppressing colorized output

\n

nvm help (or -h or --help), nvm ls, nvm ls-remote and nvm alias usually produce colorized output. You can disable colors with the --no-colors option (or by setting the environment variable TERM=dumb):

\n
nvm ls --no-colors\nnvm help --no-colors\nTERM=dumb nvm ls
\n

Restoring PATH

\n

To restore your PATH, you can deactivate it:

\n
nvm deactivate
\n

Set default node version

\n

To set a default Node version to be used in any new shell, use the alias 'default':

\n
nvm alias default node # this refers to the latest installed version of node\nnvm alias default 18 # this refers to the latest installed v18.x version of node\nnvm alias default 18.12  # this refers to the latest installed v18.12.x version of node
\n

Use a mirror of node binaries

\n

To use a mirror of the node binaries, set $NVM_NODEJS_ORG_MIRROR:

\n
export NVM_NODEJS_ORG_MIRROR=https://nodejs.org/dist\nnvm install node\n\nNVM_NODEJS_ORG_MIRROR=https://nodejs.org/dist nvm install 4.2
\n

To use a mirror of the io.js binaries, set $NVM_IOJS_ORG_MIRROR:

\n
export NVM_IOJS_ORG_MIRROR=https://iojs.org/dist\nnvm install iojs-v1.0.3\n\nNVM_IOJS_ORG_MIRROR=https://iojs.org/dist nvm install iojs-v1.0.3
\n

nvm use will not, by default, create a \"current\" symlink. Set $NVM_SYMLINK_CURRENT to \"true\" to enable this behavior, which is sometimes useful for IDEs. Note that using nvm in multiple shell tabs with this environment variable enabled can cause race conditions.

\n

Pass Authorization header to mirror

\n

To pass an Authorization header through to the mirror url, set $NVM_AUTH_HEADER

\n
NVM_AUTH_HEADER=\"Bearer secret-token\" nvm install node
\n

.nvmrc

\n

You can create a .nvmrc file containing a node version number (or any other string that nvm understands; see nvm --help for details) in the project root directory (or any parent directory).
\nAfterwards, nvm use, nvm install, nvm exec, nvm run, and nvm which will use the version specified in the .nvmrc file if no version is supplied on the command line.

\n

For example, to make nvm default to the latest 5.9 release, the latest LTS version, or the latest node version for the current directory:

\n
$ echo \"5.9\" > .nvmrc\n\n$ echo \"lts/*\" > .nvmrc # to default to the latest LTS version\n\n$ echo \"node\" > .nvmrc # to default to the latest version
\n

[NB these examples assume a POSIX-compliant shell version of echo. If you use a Windows cmd development environment, eg the .nvmrc file is used to configure a remote Linux deployment, then keep in mind the \"s will be copied leading to an invalid file. Remove them.]

\n

Then when you run nvm use:

\n
$ nvm use\nFound '/path/to/project/.nvmrc' with version <5.9>\nNow using node v5.9.1 (npm v3.7.3)
\n

Running nvm install will also switch over to the correct version, but if the correct node version isn't already installed, it will install it for you.

\n
$ nvm install\nFound '/path/to/project/.nvmrc' with version <5.9>\nDownloading and installing node v5.9.1...\nDownloading https://nodejs.org/dist/v5.9.1/node-v5.9.1-linux-x64.tar.xz...\n#################################################################################### 100.0%\nComputing checksum with sha256sum\nChecksums matched!\nNow using node v5.9.1 (npm v3.7.3)
\n

nvm use et. al. will traverse directory structure upwards from the current directory looking for the .nvmrc file. In other words, running nvm use et. al. in any subdirectory of a directory with an .nvmrc will result in that .nvmrc being utilized.

\n

The contents of a .nvmrc file must contain precisely one <version> (as described by nvm --help) followed by a newline. .nvmrc files may also have comments. The comment delimiter is #, and it and any text after it, as well as blank lines, and leading and trailing white space, will be ignored when parsing.

\n

Key/value pairs using = are also allowed and ignored, but are reserved for future use, and may cause validation errors in the future.

\n

Run npx nvmrc to validate an .nvmrc file. If that tool’s results do not agree with nvm, one or the other has a bug - please file an issue.

\n

Deeper Shell Integration

\n

You can use nvshim to shim the node, npm, and npx bins to automatically use the nvm config in the current directory. nvshim is not supported by the nvm maintainers. Please report issues to the nvshim team.

\n

If you prefer a lighter-weight solution, the recipes below have been contributed by nvm users. They are not supported by the nvm maintainers. We are, however, accepting pull requests for more examples.

\n

Calling nvm use automatically in a directory with a .nvmrc file

\n

In your profile (~/.bash_profile, ~/.zshrc, ~/.profile, or ~/.bashrc), add the following to nvm use whenever you enter a new directory:

\n
bash
\n

Put the following at the end of your $HOME/.bashrc:

\n
cdnvm() {\n    command cd \"$@\" || return $?\n    nvm_path=\"$(nvm_find_up .nvmrc | command tr -d '\\n')\"\n\n    # If there are no .nvmrc file, use the default nvm version\n    if [[ ! $nvm_path = *[^[:space:]]* ]]; then\n\n        declare default_version\n        default_version=\"$(nvm version default)\"\n\n        # If there is no default version, set it to `node`\n        # This will use the latest version on your machine\n        if [ $default_version = 'N/A' ]; then\n            nvm alias default node\n            default_version=$(nvm version default)\n        fi\n\n        # If the current version is not the default version, set it to use the default version\n        if [ \"$(nvm current)\" != \"${default_version}\" ]; then\n            nvm use default\n        fi\n    elif [[ -s \"${nvm_path}/.nvmrc\" && -r \"${nvm_path}/.nvmrc\" ]]; then\n        declare nvm_version\n        nvm_version=$(<\"${nvm_path}\"/.nvmrc)\n\n        declare locally_resolved_nvm_version\n        # `nvm ls` will check all locally-available versions\n        # If there are multiple matching versions, take the latest one\n        # Remove the `->` and `*` characters and spaces\n        # `locally_resolved_nvm_version` will be `N/A` if no local versions are found\n        locally_resolved_nvm_version=$(nvm ls --no-colors \"${nvm_version}\" | command tail -1 | command tr -d '\\->*' | command tr -d '[:space:]')\n\n        # If it is not already installed, install it\n        # `nvm install` will implicitly use the newly-installed version\n        if [ \"${locally_resolved_nvm_version}\" = 'N/A' ]; then\n            nvm install \"${nvm_version}\";\n        elif [ \"$(nvm current)\" != \"${locally_resolved_nvm_version}\" ]; then\n            nvm use \"${nvm_version}\";\n        fi\n    fi\n}\n\nalias cd='cdnvm'\ncdnvm \"$PWD\" || exit
\n

This alias would search 'up' from your current directory in order to detect a .nvmrc file. If it finds it, it will switch to that version; if not, it will use the default version.

\n
zsh
\n

This shell function will install (if needed) and nvm use the specified Node version when an .nvmrc is found, and nvm use default otherwise.

\n

Put this into your $HOME/.zshrc to call nvm use automatically whenever you enter a directory that contains an
\n.nvmrc file with a string telling nvm which node to use:

\n
# place this after nvm initialization!\nautoload -U add-zsh-hook\n\nload-nvmrc() {\n  local nvmrc_path\n  nvmrc_path=\"$(nvm_find_nvmrc)\"\n\n  if [ -n \"$nvmrc_path\" ]; then\n    local nvmrc_node_version\n    nvmrc_node_version=$(nvm version \"$(cat \"${nvmrc_path}\")\")\n\n    if [ \"$nvmrc_node_version\" = \"N/A\" ]; then\n      nvm install\n    elif [ \"$nvmrc_node_version\" != \"$(nvm version)\" ]; then\n      nvm use\n    fi\n  elif [ -n \"$(PWD=$OLDPWD nvm_find_nvmrc)\" ] && [ \"$(nvm version)\" != \"$(nvm version default)\" ]; then\n    echo \"Reverting to nvm default version\"\n    nvm use default\n  fi\n}\n\nadd-zsh-hook chpwd load-nvmrc\nload-nvmrc
\n

After saving the file, run source ~/.zshrc to reload the configuration with the latest changes made.

\n
fish
\n

This requires that you have bass installed.

\n
# ~/.config/fish/functions/nvm.fish\nfunction nvm\n  bass source ~/.nvm/nvm.sh --no-use ';' nvm $argv\nend\n\n# ~/.config/fish/functions/nvm_find_nvmrc.fish\nfunction nvm_find_nvmrc\n  bass source ~/.nvm/nvm.sh --no-use ';' nvm_find_nvmrc\nend\n\n# ~/.config/fish/functions/load_nvm.fish\nfunction load_nvm --on-variable=\"PWD\"\n  set -l default_node_version (nvm version default)\n  set -l node_version (nvm version)\n  set -l nvmrc_path (nvm_find_nvmrc)\n  if test -n \"$nvmrc_path\"\n    set -l nvmrc_node_version (nvm version (cat $nvmrc_path))\n    if test \"$nvmrc_node_version\" = \"N/A\"\n      nvm install (cat $nvmrc_path)\n    else if test \"$nvmrc_node_version\" != \"$node_version\"\n      nvm use $nvmrc_node_version\n    end\n  else if test \"$node_version\" != \"$default_node_version\"\n    echo \"Reverting to default Node version\"\n    nvm use default\n  end\nend\n\n# ~/.config/fish/config.fish\n# You must call it on initialization or listening to directory switching won't work\nload_nvm > /dev/stderr
\n

Running Tests

\n

Tests are written in Urchin. Install Urchin (and other dependencies) like so:

\n
npm install\n
\n

There are slow tests and fast tests. The slow tests do things like install node
\nand check that the right versions are used. The fast tests fake this to test
\nthings like aliases and uninstalling. From the root of the nvm git repository,
\nrun the fast tests like this:

\n
npm run test/fast\n
\n

Run the slow tests like this:

\n
npm run test/slow\n
\n

Run all of the tests like this:

\n
npm test\n
\n

Nota bene: Avoid running nvm while the tests are running.

\n

Environment variables

\n

nvm exposes the following environment variables:

\n\n

Additionally, nvm modifies PATH, and, if present, MANPATH and NODE_PATH when changing versions.

\n

Bash Completion

\n

To activate, you need to source bash_completion:

\n
[[ -r $NVM_DIR/bash_completion ]] && \\. $NVM_DIR/bash_completion
\n

Put the above sourcing line just below the sourcing line for nvm in your profile (.bashrc, .bash_profile).

\n

Usage

\n

nvm:

\n
\n

$ nvm Tab

\n
\n
alias               deactivate          install             list-remote         reinstall-packages  uninstall           version\ncache               exec                install-latest-npm  ls                  run                 unload              version-remote\ncurrent             help                list                ls-remote           unalias             use                 which
\n

nvm alias:

\n
\n

$ nvm alias Tab

\n
\n
default      iojs         lts/*        lts/argon    lts/boron    lts/carbon   lts/dubnium  lts/erbium   node         stable       unstable
\n
\n

$ nvm alias my_alias Tab

\n
\n
v10.22.0       v12.18.3      v14.8.0
\n

nvm use:

\n
\n

$ nvm use Tab

\n
\n
my_alias        default        v10.22.0       v12.18.3      v14.8.0\n
\n

nvm uninstall:

\n
\n

$ nvm uninstall Tab

\n
\n
my_alias        default        v10.22.0       v12.18.3      v14.8.0\n
\n

Compatibility Issues

\n

nvm will encounter some issues if you have some non-default settings set. (see #606)
\nThe following are known to cause issues:

\n

Inside ~/.npmrc:

\n
prefix='some/path'
\n

Environment Variables:

\n
$NPM_CONFIG_PREFIX\n$PREFIX
\n

Shell settings:

\n
set -e
\n

Installing nvm on Alpine Linux

\n

In order to provide the best performance (and other optimizations), nvm will download and install pre-compiled binaries for Node (and npm) when you run nvm install X. The Node project compiles, tests and hosts/provides these pre-compiled binaries which are built for mainstream/traditional Linux distributions (such as Debian, Ubuntu, CentOS, RedHat et al).

\n

Alpine Linux, unlike mainstream/traditional Linux distributions, is based on BusyBox, a very compact (~5MB) Linux distribution. BusyBox (and thus Alpine Linux) uses a different C/C++ stack to most mainstream/traditional Linux distributions - musl. This makes binary programs built for such mainstream/traditional incompatible with Alpine Linux, thus we cannot simply nvm install X on Alpine Linux and expect the downloaded binary to run correctly - you'll likely see \"...does not exist\" errors if you try that.

\n

There is a -s flag for nvm install which requests nvm download Node source and compile it locally.

\n

If installing nvm on Alpine Linux is still what you want or need to do, you should be able to achieve this by running the following from you Alpine Linux shell, depending on which version you are using:

\n

Alpine Linux 3.13+

\n
apk add -U curl bash ca-certificates openssl ncurses coreutils python3 make gcc g++ libgcc linux-headers grep util-linux binutils findutils\ncurl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash
\n

Alpine Linux 3.5 - 3.12

\n
apk add -U curl bash ca-certificates openssl ncurses coreutils python2 make gcc g++ libgcc linux-headers grep util-linux binutils findutils\ncurl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash
\n

Note: Alpine 3.5 can only install NodeJS versions up to v6.9.5, Alpine 3.6 can only install versions up to v6.10.3, Alpine 3.7 installs versions up to v8.9.3, Alpine 3.8 installs versions up to v8.14.0, Alpine 3.9 installs versions up to v10.19.0, Alpine 3.10 installs versions up to v10.24.1, Alpine 3.11 installs versions up to v12.22.6, Alpine 3.12 installs versions up to v12.22.12, Alpine 3.13 & 3.14 install versions up to v14.20.0, Alpine 3.15 & 3.16 install versions up to v16.16.0 (These are all versions on the main branch). Alpine 3.5 - 3.12 required the package python2 to build NodeJS, as they are older versions to build. Alpine 3.13+ requires python3 to successfully build newer NodeJS versions, but you can use python2 with Alpine 3.13+ if you need to build versions of node supported in Alpine 3.5 - 3.15, you just need to specify what version of NodeJS you need to install in the package install script.

\n

The Node project has some desire but no concrete plans (due to the overheads of building, testing and support) to offer Alpine-compatible binaries.

\n

As a potential alternative, @mhart (a Node contributor) has some Docker images for Alpine Linux with Node and optionally, npm, pre-installed.

\n

\n

Uninstalling / Removal

\n

Manual Uninstall

\n

To remove nvm manually, execute the following:

\n

First, use nvm unload to remove the nvm command from your terminal session and delete the installation directory:

\n
$ nvm_dir=\"${NVM_DIR:-~/.nvm}\"\n$ nvm unload\n$ rm -rf \"$nvm_dir\"
\n

Edit ~/.bashrc (or other shell resource config) and remove the lines below:

\n
export NVM_DIR=\"$HOME/.nvm\"\n[ -s \"$NVM_DIR/nvm.sh\" ] && \\. \"$NVM_DIR/nvm.sh\" # This loads nvm\n[[ -r $NVM_DIR/bash_completion ]] && \\. $NVM_DIR/bash_completion
\n

Docker For Development Environment

\n

To make the development and testing work easier, we have a Dockerfile for development usage, which is based on Ubuntu 18.04 base image, prepared with essential and useful tools for nvm development, to build the docker image of the environment, run the docker command at the root of nvm repository:

\n
$ docker build -t nvm-dev .
\n

This will package your current nvm repository with our pre-defined development environment into a docker image named nvm-dev, once it's built with success, validate your image via docker images:

\n
$ docker images\n\nREPOSITORY         TAG                 IMAGE ID            CREATED             SIZE\nnvm-dev            latest              9ca4c57a97d8        7 days ago          650 MB
\n

If you got no error message, now you can easily involve in:

\n
$ docker run -h nvm-dev -it nvm-dev\n\nnvm@nvm-dev:~/.nvm$
\n

Please note that it'll take about 8 minutes to build the image and the image size would be about 650MB, so it's not suitable for production usage.

\n

For more information and documentation about docker, please refer to its official website:

\n\n

Problems

\n\n
nvm install -s 0.8.6
\n\n

macOS Troubleshooting

\n

nvm node version not found in vim shell

\n

If you set node version to a version other than your system node version nvm use 6.2.1 and open vim and run :!node -v you should see v6.2.1 if you see your system version v0.12.7. You need to run:

\n
sudo chmod ugo-x /usr/libexec/path_helper
\n

More on this issue in dotphiles/dotzsh.

\n

nvm is not compatible with the npm config \"prefix\" option

\n

Some solutions for this issue can be found here

\n

There is one more edge case causing this issue, and that's a mismatch between the $HOME path and the user's home directory's actual name.

\n

You have to make sure that the user directory name in $HOME and the user directory name you'd see from running ls /Users/ are capitalized the same way (See this issue).

\n

To change the user directory and/or account name follow the instructions here

\n

Homebrew makes zsh directories unsecure

\n
zsh compinit: insecure directories, run compaudit for list.\nIgnore insecure directories and continue [y] or abort compinit [n]? y
\n

Homebrew causes insecure directories like /usr/local/share/zsh/site-functions and /usr/local/share/zsh. This is not an nvm problem - it is a homebrew problem. Refer here for some solutions related to the issue.

\n

Macs with Apple Silicon chips

\n

Experimental support for the Apple Silicon chip architecture was added in node.js v15.3 and full support was added in v16.0.
\nBecause of this, if you try to install older versions of node as usual, you will probably experience either compilation errors when installing node or out-of-memory errors while running your code.

\n

So, if you want to run a version prior to v16.0 on an Apple Silicon Mac, it may be best to compile node targeting the x86_64 Intel architecture so that Rosetta 2 can translate the x86_64 processor instructions to ARM-based Apple Silicon instructions.
\nHere's what you will need to do:

\n\n

Now you should be able to use node as usual.

\n

WSL Troubleshooting

\n

If you've encountered this error on WSL-2:

\n
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash\n% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                Dload  Upload  Total   Spent    Left  Speed\n0     0    0     0    0     0      0      0 --:--:--  0:00:09 --:--:--     0curl: (6) Could not resolve host: raw.githubusercontent.com
\n

It may be due to your antivirus, VPN, or other reasons.

\n

Where you can ping 8.8.8.8 while you can't ping google.com

\n

This could simply be solved by running this in your root directory:

\n
sudo rm /etc/resolv.conf\nsudo bash -c 'echo \"nameserver 8.8.8.8\" > /etc/resolv.conf'\nsudo bash -c 'echo \"[network]\" > /etc/wsl.conf'\nsudo bash -c 'echo \"generateResolvConf = false\" >> /etc/wsl.conf'\nsudo chattr +i /etc/resolv.conf
\n

This deletes your resolv.conf file that is automatically generated when you run WSL, creates a new file and puts nameserver 8.8.8.8, then creates a wsl.conf file and adds [network] and generateResolveConf = false to prevent auto-generation of that file.

\n

You can check the contents of the file by running:

\n
cat /etc/resolv.conf
\n

Maintainers

\n

Currently, the sole maintainer is @ljharb - more maintainers are quite welcome, and we hope to add folks to the team over time. Governance will be re-evaluated as the project evolves.

\n

Project Support

\n

Only the latest version (v0.40.3 at this time) is supported.

\n

Enterprise Support

\n

If you are unable to update to the latest version of nvm, our partners provide commercial security fixes for all unsupported versions:

\n\n

License

\n

See LICENSE.md.

\n

Copyright notice

\n

Copyright OpenJS Foundation and nvm contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.
\nThe OpenJS Foundation | Terms of Use | Privacy Policy | Bylaws | Code of Conduct | Trademark Policy | Trademark List | Cookie Policy

","updatedAt":"2025-05-21T16:13:57Z","upvoteCount":null,"author":{"login":"eryajf","avatarUrl":"https://avatars.githubusercontent.com/u/33259379?u=e4a4090a38ac2473aaed4ef9945233636776c6c3&v=4","url":"https://github.com/eryajf"},"category":null,"labels":{"edges":[{"node":{"name":"更多","color":"25B472"}},{"node":{"name":"Version-Switch-Tools","color":"8ff216"}},{"node":{"name":"nvm-sh","color":"677910"}}]},"comments":{"edges":[]}}},"pageContext":{"number":408,"previous":{"title":"coreybutler/nvm-windows: 用于 Windows 系统中多个 Node 版本的管理与切换","number":407},"next":{"title":"keyval-dev/odigos: 分布式跟踪，无需更改代码。🚀 使用 OpenTelemetry 和 eBPF 即时监控任何应用程序","number":409}}}, "staticQueryHashes": ["151096407","2861350382"]}