より軽量なソリューションを好む場合は、以下のレシピがユーザーから提供されています。メンテナによってサポートされていません。ただし、より多くの例のプルリクエストを受け付けています。

nvm

nvm

バッシュ

自動的に呼び出す

nvm use

あなたの最後に以下を入れてください:

$HOME/.bashrc

cdnvm() {
    command cd "$@" || return $?
    nvm_path=$(nvm_find_up .nvmrc | tr -d '\n')

    # If there are no .nvmrc file, use the default nvm version
    if [[ ! $nvm_path = *[^[:space:]]* ]]; then

        declare default_version;
        default_version=$(nvm version default);

        # If there is no default version, set it to `node`
        # This will use the latest version on your machine
        if [[ $default_version == "N/A" ]]; then
            nvm alias default node;
            default_version=$(nvm version default);
        fi

        # If the current version is not the default version, set it to use the default version
        if [[ $(nvm current) != "$default_version" ]]; then
            nvm use default;
        fi

    elif [[ -s $nvm_path/.nvmrc && -r $nvm_path/.nvmrc ]]; then
        declare nvm_version
        nvm_version=$(<"$nvm_path"/.nvmrc)

        declare locally_resolved_nvm_version
        # `nvm ls` will check all locally-available versions
        # If there are multiple matching versions, take the latest one
        # Remove the `->` and `*` characters and spaces
        # `locally_resolved_nvm_version` will be `N/A` if no local versions are found
        locally_resolved_nvm_version=$(nvm ls --no-colors "$nvm_version" | tail -1 | tr -d '\->*' | tr -d '[:space:]')

        # If it is not already installed, install it
        # `nvm install` will implicitly use the newly-installed version
        if [[ "$locally_resolved_nvm_version" == "N/A" ]]; then
            nvm install "$nvm_version";
        elif [[ $(nvm current) != "$locally_resolved_nvm_version" ]]; then
            nvm use "$nvm_version";
        fi
    fi
}
alias cd='cdnvm'
cd "$PWD"

このエイリアスは、ファイルを検出するために現在のディレクトリから「up」を検索します。見つかった場合は、そのバージョンに切り替わります。そうでない場合は、デフォルトバージョンが使用されます。

.nvmrc

ティッカー

ファイルのあるディレクトリで自動的に呼び出す

nvm use

.nvmrc

これをuに入れて、nvmにどのノードを指示するかを指示する文字列を含むファイルを含むディレクトリに入るたびに自動的に呼び出します。

$HOME/.zshrc

nvm use

.nvmrc

use

# place this after nvm initialization!
autoload -U add-zsh-hook
load-nvmrc() {
  local nvmrc_path="$(nvm_find_nvmrc)"

  if [ -n "$nvmrc_path" ]; then
    local nvmrc_node_version=$(nvm version "$(cat "${nvmrc_path}")")

    if [ "$nvmrc_node_version" = "N/A" ]; then
      nvm install
    elif [ "$nvmrc_node_version" != "$(nvm version)" ]; then
      nvm use
    fi
  elif [ -n "$(PWD=$OLDPWD nvm_find_nvmrc)" ] && [ "$(nvm version)" != "$(nvm version default)" ]; then
    echo "Reverting to nvm default version"
    nvm use default
  fi
}
add-zsh-hook chpwd load-nvmrc
load-nvmrc

魚

ファイルのあるディレクトリで自動的に呼び出す

nvm use

.nvmrc

This requires that you have bass installed.

# ~/.config/fish/functions/nvm.fish
function nvm
  bass source ~/.nvm/nvm.sh --no-use ';' nvm $argv
end

# ~/.config/fish/functions/nvm_find_nvmrc.fish
function nvm_find_nvmrc
  bass source ~/.nvm/nvm.sh --no-use ';' nvm_find_nvmrc
end

# ~/.config/fish/functions/load_nvm.fish
function load_nvm --on-variable="PWD"
  set -l default_node_version (nvm version default)
  set -l node_version (nvm version)
  set -l nvmrc_path (nvm_find_nvmrc)
  if test -n "$nvmrc_path"
    set -l nvmrc_node_version (nvm version (cat $nvmrc_path))
    if test "$nvmrc_node_version" = "N/A"
      nvm install (cat $nvmrc_path)
    else if test "$nvmrc_node_version" != "$node_version"
      nvm use $nvmrc_node_version
    end
  else if test "$node_version" != "$default_node_version"
    echo "Reverting to default Node version"
    nvm use default
  end
end

# ~/.config/fish/config.fish
# You must call it on initialization or listening to directory switching won't work
load_nvm > /dev/stderr

Running Tests

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

npm install

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

npm run test/fast

Run the slow tests like this:

npm run test/slow

Run all of the tests like this:

npm test

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

Environment variables

nvm exposes the following environment variables:

• NVM_DIR

  - nvm's installation directory.

• NVM_BIN

  - where node, npm, and global packages for the active version of node are installed.

• NVM_INC

  - node's include file directory (useful for building C/C++ addons for node).

• NVM_CD_FLAGS

  - used to maintain compatibility with zsh.

• NVM_RC_VERSION

  - version from .nvmrc file if being used.

Additionally, nvm modifies , and, if present, and when changing versions.

PATH

MANPATH

NODE_PATH

Bash Completion

To activate, you need to source :

bash_completion

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

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

.bashrc

.bash_profile

Usage

nvm:

$ nvm

Tab

alias               deactivate          install             list-remote         reinstall-packages  uninstall           version
cache               exec                install-latest-npm  ls                  run                 unload              version-remote
current             help                list                ls-remote           unalias             use                 which

nvm alias:

$ nvm alias

Tab

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

$ nvm alias my_alias

Tab

v10.22.0       v12.18.3      v14.8.0

nvm use:

$ nvm use

Tab

my_alias        default        v10.22.0       v12.18.3      v14.8.0

nvm uninstall:

$ nvm uninstall

Tab

my_alias        default        v10.22.0       v12.18.3      v14.8.0

Compatibility Issues

nvm

Inside :

~/.npmrc

prefix='some/path'

Environment Variables:

$NPM_CONFIG_PREFIX
$PREFIX

Shell settings:

set -e

Installing nvm on Alpine Linux

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 . 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).

nvm install X

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 on Alpine Linux and expect the downloaded binary to run correctly - you'll likely see "...does not exist" errors if you try that.

nvm install X

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

-s

nvm install

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:

Alpine Linux 3.13+

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

Alpine Linux 3.5 - 3.12

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

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

python3

python2

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

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

Uninstalling / Removal

Manual Uninstall

To remove manually, execute the following:

nvm

$ rm -rf "$NVM_DIR"

Edit (or other shell resource config) and remove the lines below:

~/.bashrc

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

Docker For Development Environment

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 development, to build the docker image of the environment, run the docker command at the root of repository:

nvm

nvm

$ docker build -t nvm-dev .

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

nvm-dev

docker images

$ docker images

REPOSITORY         TAG                 IMAGE ID            CREATED             SIZE
nvm-dev            latest              9ca4c57a97d8        7 days ago          650 MB

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

$ docker run -h nvm-dev -it nvm-dev

nvm@nvm-dev:~/.nvm$

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.

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

• https://www.docker.com/
• https://docs.docker.com/

Problems

• If you try to install a node version and the installation fails, be sure to run to delete cached node downloads, or you might get an error like the following:

  nvm cache clear

  curl: (33) HTTP server doesn't seem to support byte ranges. Cannot resume.

• Where's my ? Check out #43

  sudo node

• After the v0.8.6 release of node, nvm tries to install from binary packages. But in some systems, the official binary packages don't work due to incompatibility of shared libs. In such cases, use option to force install from source:

  -s

nvm install -s 0.8.6

• If setting the alias does not establish the node version in new shells (i.e. yields ), ensure that the system's node is set before the source line in your shell profile (see #658

  default

  nvm current

  system

  PATH

  nvm.sh

  )

macOS Troubleshooting

nvm node version not found in vim shell

If you set node version to a version other than your system node version and open vim and run you should see if you see your system version . You need to run:

nvm use 6.2.1

:!node -v

v6.2.1

v0.12.7

sudo chmod ugo-x /usr/libexec/path_helper

More on this issue in dotphiles/dotzsh.

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

Some solutions for this issue can be found here

There is one more edge case causing this issue, and that's a mismatch between the

$HOME

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

$HOME

ls /Users/

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

Homebrew makes zsh directories unsecure

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

Homebrew causes insecure directories like and . This is not an problem - it is a homebrew problem. Refer here for some solutions related to the issue.

/usr/local/share/zsh/site-functions

/usr/local/share/zsh

nvm

Macs with M1 chip

Experimental support for the M1 architecture was added in node.js v15.3 and full support was added in v16.0. Because 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.

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

x86_64

x86_64

• Install Rosetta, if you haven't already done so

  $ softwareupdate --install-rosetta

  You might wonder, "how will my M1 Mac know to use Rosetta for a version of node compiled for an Intel chip?". If an executable contains only Intel instructions, macOS will automatically use Rosetta to translate the instructions.

• Open a shell that's running using Rosetta

  $ arch -x86_64 zsh

  Note: This same thing can also be accomplished by finding the Terminal or iTerm App in Finder, right clicking, selecting "Get Info", and then checking the box labeled "Open using Rosetta".

  Note: This terminal session is now running in . If is not the shell you typically use, may not be 'd automatically like it probably is for your usual shell through your dotfiles. If that's the case, make sure to source .

  zsh

  zsh

  nvm

  source

  nvm

  $ source "${NVM_DIR}/nvm.sh"

• Install whatever older version of node you are interested in. Let's use 12.22.1 as an example. This will fetch the node source code and compile it, which will take several minutes.

  $ nvm install v12.22.1 --shared-zlib

  Note: You're probably curious why is included. There's a bug in recent versions of Apple's system compiler. If one of these broken versions is installed on your system, the above step will likely still succeed even if you didn't include the flag. However, later, when you attempt to something using your old version of node.js, you will see errors. If you want to avoid the possible hassle of dealing with this, include that flag. For more details, see this issue and this comment

  --shared-zlib

  clang

  --shared-zlib

  npm install

  incorrect data check

• Exit back to your native shell.

  $ exit
  $ arch
  arm64

  Note: If you selected the box labeled "Open using Rosetta" rather than running the CLI command in the second step, you will see here. Unless you have another reason to have that box selected, you can deselect it now.

  i386

• Check to make sure the architecture is correct. is the abbreviation for , which is what you want to see.

  x64

  x86_64

  $ node -p process.arch
  x64

Now you should be able to use node as usual.

WSL Troubleshooting

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

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

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

Where you can while you can't

ping 8.8.8.8

ping google.com

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

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

これにより、WSL の実行時に自動的に生成されるファイルが削除され、新しいファイルが作成されて put 、ファイルが作成され、そのファイルの自動生成が防止されます。

resolve.conf

nameserver 8.8.8.8

wsl.conf

[network]

generateResolveConf = false

ファイルの内容を確認するには、次のコマンドを実行します。

cat /etc/resolv.conf

メンテナ

現在、唯一のメンテナは@ljharbです - より多くのメンテナを歓迎しており、時間の経過とともにチームに人々を追加したいと考えています。ガバナンスは、プロジェクトの進展に合わせて再評価されます。

ライセンス

LICENSE.md を参照してください。

著作権表示

著作権OpenJS財団と貢献者。全著作権所有。OpenJS財団は登録商標を有し、商標を使用しています。OpenJS財団の商標のリストについては、商標ポリシーと商標リストをご覧ください。Node.jsはJoyent, Inc.の商標であり、その許可を得て使用しています。OpenJS Foundationの商標リストに記載されていない商標およびロゴは、それぞれの所有者の商標™または登録商標®です。それらの使用は、それらとの提携またはそれらによる承認を意味するものではありません。

nvm

OpenJS Foundation |利用規約 |プライバシーポリシー |OpenJS財団細則 |商標ポリシー|商標リスト |クッキーポリシー