1. Node Version Manager

1.1. Table of Contents

Installation
Usage
License
Running tests
Bash completion
- Usage
Compatibility Issues
Installing nvm on Alpine Linux
Docker for development environment
Problems
Mac OS "troubleshooting"

1.2. 安装

1.2.1. 安装脚本

你可以使用cURL的安装脚本来安装和更新：

curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.6/install.sh | bash

或者 Wget:

wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.33.6/install.sh | bash

_{这段脚本将克隆 nvm库到 ~/.nvm ，请添加source 行到配置文件 (~/.bash_profile, ~/.zshrc, ~/.profile, or ~/.bashrc).}

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

你可以自定义安装 source, directory, profile, 和 version，请使用 NVM_SOURCE, NVM_DIR, PROFILE, 和 NODE_VERSION 变量. Eg: curl ... | NVM_DIR=/usr/local/nvm bash for a global install.

_{NB. The installer can use git, curl, or wget to download nvm, whatever is available.}

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.

Note: On OS X, if you get nvm: command not found after running the install script, one of the following might be the reason:-

your system may not have a [.bash_profile file] where the command is set up. Simply create one with touch ~/.bash_profile and run the install script again
you might need to restart your terminal instance. Try opening a new tab/window in your terminal and retry.

If the above doesn't fix the problem, open your .bash_profile and add the following line of code:

source ~/.bashrc

For more information about this issue and possible workarounds, please refer here

1.2.2. Verify installation

To verify that nvm has been installed, do:

command -v nvm

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.

1.2.3. Important Notes

If you're running a system without prepackaged binary available, which means you're going to install nodejs 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.

Note: nvm does not support Windows (see #284). Two alternatives exist, which are neither supported nor developed by us:

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

bass allows you to use utilities written for Bash in fish shell
fast-nvm-fish only works with version numbers (not aliases) but doesn't significantly slow your shell startup
plugin-nvm plugin for Oh My Fish, which makes nvm and its completions available in fish shell
fnm - fisherman-based version manager for fish

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:

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:

How to Install Command Line Tools in OS X Mavericks & Yosemite (Without Xcode)

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

When using nvm you do not need sudo to globally install a module with npm -g, so instead of doing sudo npm install -g grunt, do instead npm install -g grunt
If you have an ~/.npmrc file, make sure it does not contain any prefix settings (which is not compatible with nvm)
You can (but should not?) keep your previous "system" node install, but nvm will only be available to your user account (the one used to install nvm). This might cause version mismatches, as other users will be using /usr/local/lib/node_modules/* VS your user account using ~/.nvm/versions/node/vX.X.X/lib/node_modules/*

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.

Note: If you're using zsh you can easily install nvm as a zsh plugin. Install zsh-nvm and run nvm upgrade to upgrade.

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, so the minimum required git version is v1.7.0 and we recommend v1.7.9.5 as it's the default version of the widely used Ubuntu 12.04 LTS. If you are interested in the problem we mentioned here, please refer to GitHub's HTTPS cloning errors article.

1.2.4. Git 安装

如果你已经安装了 git (需要 git v1.7+):

在用户配置文件的根目录中克隆这个"repo"
- 从任何地方运行cd ~/ ，然后运行 git clone https://github.com/creationix/nvm.git .nvm
cd ~/.nvm and check out the latest version with git checkout v0.33.6
activate nvm by sourcing it from your shell: . nvm.sh

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

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

1.2.5. Manual Install

For a fully manual install, create a folder somewhere in your filesystem with the nvm.sh file inside it. I put mine in ~/.nvm and added the following to the nvm.sh file.

export NVM_DIR="$HOME/.nvm" && (
  git clone https://github.com/creationix/nvm.git "$NVM_DIR"
  cd "$NVM_DIR"
  git checkout `git describe --abbrev=0 --tags --match "v[0-9]*" origin`
) && . "$NVM_DIR/nvm.sh"

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

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

1.2.6. Manual upgrade

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

change to the $NVM_DIR
pull down the latest changes
check out the latest version
activate the new version

(
  cd "$NVM_DIR"
  git fetch origin
  git checkout `git describe --abbrev=0 --tags --match "v[0-9]*" origin`
) && . "$NVM_DIR/nvm.sh"

1.3. 用法

要下载、编译和安装最新的node版本，请执行如下:

nvm install node

然后在任何一个新的shell中使用已安装的版本:

nvm use node

或者你可以直接运行它:

nvm run node --version

或者，您可以在子shell中使用所需版本的node运行任意的命令，并使用所需版本的node:

nvm exec 4.2 node --version

您还可以将可执行文件的路径设置为被安装的位置:

nvm which 5.0

替代像 "0.10" or "5.0" 或 "4.2.1"这样的版本指针，可以通过nvm install, nvm use, nvm run, nvm exec, nvm which等等使用下面特别的默认别名：

node: 这将安装最新版本的 node
iojs: 这将安装最新版本的 io.js
stable: 稳定。这个别名已被弃用，它只适用于 node v0.12 和更早的版本。目前, 这是node的别名。
unstable: 不稳定。这个别名指向node v0.11 - 最后一个 "unstable" node 发布, 自 1.0以后, 所有 node 版本都是稳定的。(在semver中，版本的通信易断裂，不稳定).

1.3.1. 长期支持（LST）

Node有一个用于长期支持(LTS)的时间表。您可以在别名引用LTS版本；带有lts/*记号的.nvmrc文件用于最新的LTS；lts/argon用于"argon"系列的LST发布版本。此外，下面的命令支持LTS参数:

nvm install --lts / nvm install --lts=argon / nvm install 'lts/*' / nvm install lts/argon
nvm uninstall --lts / nvm uninstall --lts=argon / nvm uninstall 'lts/*' / nvm uninstall lts/argon
nvm use --lts / nvm use --lts=argon / nvm use 'lts/*' / nvm use lts/argon
nvm exec --lts / nvm exec --lts=argon / nvm exec 'lts/*' / nvm exec lts/argon
nvm run --lts / nvm run --lts=argon / nvm run 'lts/*' / nvm run lts/argon
nvm ls-remote --lts / nvm ls-remote --lts=argon nvm ls-remote 'lts/*' / nvm ls-remote lts/argon
nvm version-remote --lts / nvm version-remote --lts=argon / nvm version-remote 'lts/*' / nvm version-remote lts/argon

任何时候，您本地的nvm副本都连接到 https://nodejs.org ，它将为所有可用的LTS线路重新创建适当的本地别名。这些别名(存储在$NVM_DIR/alias/lts中)由nvm管理，您不应该修改、删除或创建这些文件—您的更改会被取消，对这些文件的干预会从导致可能不支持的错误。

1.3.2. 在安装时迁移全局包

如果您想要安装一个新版本的Node.js并从以前的版本迁移npm包:

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

这将首先使用 "nvm version node" 来识别您正在迁移包的当前版本。然后，它将解析来自远程服务器的新版本并安装它。最后，它运行 "nvm reinstall-packages"来将npm包从先前的 Node 版本重新安装到新版本。

您还可以从特定版本的Node安装和迁移npm包:

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

1.3.3. 安装时默认的全局包

If you have a list of default packages you want installed every time you install a new version we support that too. You can add anything npm would accept as a package argument on the command line. 如果有一个默认包列表，想要每次安装一个新版本时都安装它，我们也支持这样。您可以在命令行中添加任何npm可接受的作为包参数。

# $NVM_DIR/default-packages

rimraf
object-inspect@1.0.2
stevemao/left-pad

1.3.4. io.js

如果想要安装io.js:

nvm install iojs

如果想要安装一个新版本的 io.js，并迁移之前版本的 npm包：

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

在node中迁移npm包时也提到了的指导原则也同样适用于 io.js。

1.3.5. node 的系统版本

如果您想使用系统安装的 node 版本，您可以使用特殊的默认别名"system":

nvm use system
nvm run system --version

1.3.6. 版本列表

显示已安装的node版本：

nvm ls

如果你想知道有哪些版本可供安装:

nvm ls-remote

为了恢复你的PATH，你可以停用它:

nvm deactivate

要在任何新shell中设置一个默认的节点版本，请使用别名'default':

nvm alias default node

要使用node 的二进制文件镜像$NVM_NODEJS_ORG_MIRROR:

export NVM_NODEJS_ORG_MIRROR=https://nodejs.org/dist
nvm install node

NVM_NODEJS_ORG_MIRROR=https://nodejs.org/dist nvm install 4.2

要使用 io.js 的二进制文件镜像$NVM_IOJS_ORG_MIRROR:

export NVM_IOJS_ORG_MIRROR=https://iojs.org/dist
nvm install iojs-v1.0.3

NVM_IOJS_ORG_MIRROR=https://iojs.org/dist nvm install iojs-v1.0.3

默认情况下，nvm use不会创建一个 "current" 符号链接。将$NVM_SYMLINK_CURRENT设置为"true"，以启用该行为，这在IDE中有时是有用的。注意，在启用了这个环境变量的多个shell选项卡中使用nvm可能会导致竞态(race)条件.

1.3.7. .nvmrc

你可以在根目录（或者任何父目录）创建一个包含版本号的.nvmrc文件，当在命令行中为指定版本时，nvm use, nvm install, nvm exec, nvm run, 和 nvm which 等等都将遵从.nvmrc文件。

例如，要使nvm默认为当前目录的最新的5.9发行版:

$ echo "5.9" > .nvmrc

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

然后当你运行nvm:

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

1.3.8. 深层的 Shell 集成

您可以使用avn 深入集成到您的shell中，并在更改目录时自动调用nvm。avn 不受 nvm 开发团队的支持。请向avn 团队报告问题。

如果你更喜欢轻量的解决方案，下面的配方是由 nvm 用户贡献的。它们不受 nvm 开发团队的支持。然而，我们接受了更多的示例请求。

zsh

在带有`.nvmrc`文件的目录中自动调用`nvm use`

当你输入一个包含.nvmrc文件（这个文件告诉nvm应该use哪一个node）的目录时，把这个文件放到你的$HOME/.zshrc中来自动调用nvm use：

# 在nvm初始化之后将其放置！
autoload -U add-zsh-hook
load-nvmrc() {
  local node_version="$(nvm version)"
  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" != "$node_version" ]; then
      nvm use
    fi
  elif [ "$node_version" != "$(nvm version default)" ]; then
    echo "Reverting to nvm default version"
    nvm use default
  fi
}
add-zsh-hook chpwd load-nvmrc
load-nvmrc

1.4. License

nvm is released under the MIT license.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

1.5. 运行测试

测试是用Urchin写的。安装Urchin(和其他依赖项):

npm install

有缓慢的测试和快速的测试。缓慢的测试会做一些事情，比如安装node，并检查是否使用了正确的版本。快速测试通过伪造来测试诸如别名和卸载之类的东西。从nvm git存储库的根目录中，运行如下快速测试:

npm run test/fast

运行慢测试

npm run test/slow

运行所有测试

npm test

[info] 留心:

在测试运行时避免运行nvm。

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

1.6.1. Usage

nvm:

$ nvm Tab

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

nvm alias:

$ nvm alias Tab
default
$ nvm alias my_alias Tab
v0.6.21        v0.8.26       v0.10.28

nvm use:

$ nvm use Tab

my_alias        default        v0.6.21        v0.8.26       v0.10.28

nvm uninstall:

$ nvm uninstall Tab

my_alias        default        v0.6.21        v0.8.26       v0.10.28

1.7. Compatibility Issues

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

Inside ~/.npmrc:

prefix='some/path'

Environment Variables:

$NPM_CONFIG_PREFIX
$PREFIX

Shell settings:

set -e

1.8. 在 Alpine Linux 上安装 nvm

In order to provide the best performance (and other optimisations), 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 pre-these compiled binaries which are built for mainstream/traditional Linux distributions (such as Debian, Ubuntu, CentOS, RedHat et al).

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.

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

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:

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/creationix/nvm/v0.33.6/install.sh | bash

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.

1.9. Docker for development environment

To make the development and testing work easier, we have a Dockerfile for development usage, which is based on Ubuntu 14.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:

$ docker build -t nvm-dev .

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

$ docker images

REPOSITORY         TAG                 IMAGE ID            CREATED             SIZE
nvm-dev            latest              9ca4c57a97d8        7 days ago          1.22 GB

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

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

nvm@nvm-dev:~/.nvm$

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

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

1.10. Problems

If you try to install a node version and the installation fails, be sure to delete the node downloads from src (~/.nvm/src/) or you might get an error when trying to reinstall them again or you might get an error like the following:

curl: (33) HTTP server doesn't seem to support byte ranges. Cannot resume.
Where's my sudo node? Check out #43
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 -s option to force install from source:

nvm install -s 0.8.6

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

1.11. Mac OS "troubleshooting"

nvm node version not found in vim shell

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:

sudo chmod ugo-x /usr/libexec/path_helper

指令	描述
nvm --help	显示帮助信息
nvm --version	打印nvm的版本
nvm install [-s]	Download and install a , [-s] from source. Uses .nvmrc if available

node 版本管理

1. Node Version Manager

1.1. Table of Contents

1.2. 安装

1.2.1. 安装脚本

1.2.2. Verify installation

1.2.3. Important Notes

1.2.4. Git 安装

1.2.5. Manual Install

1.2.6. Manual upgrade

1.3. 用法

1.3.1. 长期支持（LST）

1.3.2. 在安装时迁移全局包

1.3.3. 安装时默认的全局包

1.3.4. io.js

1.3.5. node 的系统版本

1.3.6. 版本列表

1.3.7. .nvmrc

1.3.8. 深层的 Shell 集成

zsh

在带有`.nvmrc`文件的目录中自动调用`nvm use`

1.4. License

1.5. 运行测试

1.6. Bash completion

1.6.1. Usage

1.7. Compatibility Issues

1.8. 在 Alpine Linux 上安装 nvm

1.9. Docker for development environment

1.10. Problems

1.11. Mac OS "troubleshooting"

results matching ""

No results matching ""

1. Node Version Manager

1.1. Table of Contents

1.2. 安装

1.2.1. 安装脚本

1.2.2. Verify installation

1.2.3. Important Notes

1.2.4. Git 安装

1.2.5. Manual Install

1.2.6. Manual upgrade

1.3. 用法

1.3.1. 长期支持（LST）

1.3.2. 在安装时迁移全局包

1.3.3. 安装时默认的全局包

1.3.4. io.js

1.3.5. node 的系统版本

1.3.6. 版本列表

1.3.7. .nvmrc

1.3.8. 深层的 Shell 集成

zsh

在带有.nvmrc文件的目录中自动调用nvm use

1.4. License

1.5. 运行测试

1.6. Bash completion

1.6.1. Usage

1.7. Compatibility Issues

1.8. 在 Alpine Linux 上安装 nvm

1.9. Docker for development environment

1.10. Problems

1.11. Mac OS "troubleshooting"

results matching ""

No results matching ""

在带有`.nvmrc`文件的目录中自动调用`nvm use`