2014-04-26 01:43:22 +08:00
# Node Version Manager [![Build Status](https://travis-ci.org/creationix/nvm.svg?branch=master)][3]
2010-04-16 01:00:34 +08:00
## Installation
2010-12-11 03:32:16 +08:00
First you'll need to make sure your system has a c++ compiler. For OSX, XCode will work, for Ubuntu, the build-essential and libssl-dev packages work.
2010-04-16 01:06:53 +08:00
2012-12-05 06:21:00 +08:00
### Install script
2014-04-26 01:43:22 +08:00
To install you could use the [install script][2] using cURL:
2012-12-05 06:21:00 +08:00
2014-04-26 15:48:06 +08:00
curl https://raw.githubusercontent.com/creationix/nvm/v0.5.1/install.sh | sh
2012-12-05 06:21:00 +08:00
or Wget:
2014-04-26 15:48:06 +08:00
wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.5.1/install.sh | sh
2012-12-05 06:21:00 +08:00
2013-12-23 01:37:08 +08:00
< sub > The script clones the nvm repository to `~/.nvm` and adds the source line to your profile (`~/.bash_profile`, `~/.zshrc` or `~/.profile` ).</ sub >
2012-12-05 06:21:00 +08:00
2013-12-23 01:37:08 +08:00
You can customize the install source, directory and profile using the `NVM_SOURCE` , `NVM_DIR` and `NVM_PROFILE` variables. Eg: `curl ... | NVM_DIR=/usr/local/nvm sh` for a global install.
< sub > *NB. The installer can use Git, cURL or Wget to download NVM, whatever is available.*< / sub >
2012-12-05 06:21:00 +08:00
### Manual install
For manual install create a folder somewhere in your filesystem with the `nvm.sh` file inside it. I put mine in a folder called `nvm` .
2010-04-16 01:14:52 +08:00
Or if you have `git` installed, then just clone it:
2013-08-10 08:04:25 +08:00
git clone https://github.com/creationix/nvm.git ~/.nvm
2010-04-16 01:00:34 +08:00
2013-08-10 17:30:25 +08:00
To activate nvm, you need to source it from your shell:
2010-04-16 01:00:34 +08:00
2013-06-15 00:26:51 +08:00
source ~/.nvm/nvm.sh
2010-12-11 03:42:19 +08:00
2013-08-10 17:30:25 +08:00
I always add this line to my `~/.bashrc` , `~/.profile` , or `~/.zshrc` file to have it automatically sourced upon login.
2010-12-11 03:42:19 +08:00
Often I also put in a line to use a specific version of node.
2013-08-16 02:25:51 +08:00
2010-04-16 01:00:34 +08:00
## Usage
2013-06-15 00:14:37 +08:00
To download, compile, and install the latest v0.10.x release of node, do this:
2010-04-16 01:00:34 +08:00
2013-06-15 00:14:37 +08:00
nvm install 0.10
2010-04-16 01:00:34 +08:00
And then in any new shell just use the installed version:
2013-06-15 00:14:37 +08:00
nvm use 0.10
2010-04-16 01:00:34 +08:00
2013-09-01 01:55:12 +08:00
You can create an `.nvmrc` file containing version number in the project root folder; run the following command to switch versions:
2013-08-16 02:25:51 +08:00
nvm use
2011-10-29 16:04:37 +08:00
Or you can just run it:
2013-06-15 00:14:37 +08:00
nvm run 0.10
2011-10-29 16:04:37 +08:00
2013-03-04 19:54:42 +08:00
If you want to see what versions are installed:
2010-04-16 01:00:34 +08:00
2010-12-11 03:32:16 +08:00
nvm ls
2010-04-16 01:03:42 +08:00
2013-03-04 19:54:42 +08:00
If you want to see what versions are available to install:
nvm ls-remote
2010-12-11 03:32:16 +08:00
To restore your PATH, you can deactivate it.
2010-04-16 01:03:42 +08:00
2010-12-11 03:32:16 +08:00
nvm deactivate
2010-05-07 07:33:46 +08:00
2011-01-23 02:16:24 +08:00
To set a default Node version to be used in any new shell, use the alias 'default':
2013-06-15 00:14:37 +08:00
nvm alias default 0.10
2011-01-23 02:16:24 +08:00
2014-02-01 02:00:19 +08:00
To use a mirror of the node binaries, set `$NVM_NODEJS_ORG_MIRROR` :
2014-01-31 11:22:44 +08:00
2014-02-01 02:00:19 +08:00
export NVM_NODEJS_ORG_MIRROR=http://nodejs.org/dist
2014-01-31 11:22:44 +08:00
nvm install 0.10
2014-02-01 02:00:19 +08:00
NVM_NODEJS_ORG_MIRROR=http://nodejs.org/dist nvm install 0.10
2012-07-20 21:30:13 +08:00
## License
2013-08-21 01:39:44 +08:00
nvm is released under the MIT license.
2012-07-20 21:30:13 +08:00
2014-02-04 09:07:56 +08:00
Copyright (C) 2010-2014 Tim Caswell
2012-07-20 21:30:13 +08:00
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.
2012-10-11 07:17:09 +08:00
## Running tests
2014-04-26 01:43:22 +08:00
Tests are written in [Urchin]. Install Urchin (and other dependencies) like so:
2012-10-11 07:17:09 +08:00
2013-12-18 05:09:55 +08:00
npm install
2012-10-11 07:17:09 +08:00
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.
2013-12-18 05:09:55 +08:00
npm run test/fast
2012-10-11 07:17:09 +08:00
Run the slow tests like this.
2013-12-18 05:09:55 +08:00
npm run test/slow
2012-10-11 07:17:09 +08:00
Run all of the tests like this
2013-12-18 05:09:55 +08:00
npm test
2012-10-11 07:17:09 +08:00
Nota bene: Avoid running nvm while the tests are running.
2012-07-20 21:30:13 +08:00
2012-04-09 14:25:49 +08:00
## 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][tab]
2013-08-16 02:25:51 +08:00
alias copy-packages help list run uninstall version
2012-04-09 14:25:49 +08:00
clear-cache deactivate install ls unalias use
nvm alias
$ nvm alias [tab][tab]
default
$ nvm alias my_alias [tab][tab]
v0.4.11 v0.4.12 v0.6.14
2013-08-16 02:25:51 +08:00
2012-04-09 14:25:49 +08:00
nvm use
$ nvm use [tab][tab]
my_alias default v0.4.11 v0.4.12 v0.6.14
2013-08-16 02:25:51 +08:00
2012-04-09 14:25:49 +08:00
nvm uninstall
$ nvm uninstall [tab][tab]
my_alias default v0.4.11 v0.4.12 v0.6.14
2013-08-16 02:25:51 +08:00
2011-11-14 21:48:56 +08:00
## Problems
2013-06-15 00:13:54 +08:00
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:
2013-08-16 02:25:51 +08:00
2011-11-14 21:48:56 +08:00
curl: (33) HTTP server doesn't seem to support byte ranges. Cannot resume.
2011-11-14 22:16:09 +08:00
Where's my 'sudo node'? Checkout this link:
2013-08-16 02:25:51 +08:00
2012-10-18 00:45:43 +08:00
https://github.com/creationix/nvm/issues/43
2012-03-07 08:34:12 +08:00
on Arch Linux and other systems using python3 by default, before running *install* you need to
export PYTHON=python2
2013-01-12 12:59:28 +08:00
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:
2013-01-12 13:40:41 +08:00
nvm install -s 0.8.6
2013-06-15 00:13:54 +08:00
2014-04-26 01:43:22 +08:00
[1]: https://github.com/creationix/nvm.git
2014-04-26 01:47:59 +08:00
[2]: https://github.com/creationix/nvm/blob/v0.5.1/install.sh
2014-04-26 01:43:22 +08:00
[3]: https://travis-ci.org/creationix/nvm
[Urchin]: https://github.com/scraperwiki/urchin