|
|
|
|
@ -70,8 +70,8 @@ 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.
|
|
|
|
|
- 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:
|
|
|
|
|
|
|
|
|
|
@ -94,26 +94,26 @@ which should output 'nvm' if the installation was successful. Please note that `
|
|
|
|
|
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](https://github.com/creationix/nvm/issues/284)). Two alternatives exist, which are neither supported nor developed by us:
|
|
|
|
|
- [nvm-windows](https://github.com/coreybutler/nvm-windows)
|
|
|
|
|
- [nodist](https://github.com/marcelklehr/nodist)
|
|
|
|
|
- [nvm-windows](https://github.com/coreybutler/nvm-windows)
|
|
|
|
|
- [nodist](https://github.com/marcelklehr/nodist)
|
|
|
|
|
|
|
|
|
|
**Note:** `nvm` does not support [Fish] either (see [#303](https://github.com/creationix/nvm/issues/303)). Alternatives exist, which are neither supported nor developed by us:
|
|
|
|
|
- [bass](https://github.com/edc/bass) allows you to use utilities written for Bash in fish shell
|
|
|
|
|
- [fast-nvm-fish](https://github.com/brigand/fast-nvm-fish) only works with version numbers (not aliases) but doesn't significantly slow your shell startup
|
|
|
|
|
- [plugin-nvm](https://github.com/derekstavis/plugin-nvm) plugin for [Oh My Fish](https://github.com/oh-my-fish/oh-my-fish), which makes nvm and its completions available in fish shell
|
|
|
|
|
- [fnm](https://github.com/fisherman/fnm) - [fisherman](https://github.com/fisherman/fisherman)-based version manager for fish
|
|
|
|
|
- [bass](https://github.com/edc/bass) allows you to use utilities written for Bash in fish shell
|
|
|
|
|
- [fast-nvm-fish](https://github.com/brigand/fast-nvm-fish) only works with version numbers (not aliases) but doesn't significantly slow your shell startup
|
|
|
|
|
- [plugin-nvm](https://github.com/derekstavis/plugin-nvm) plugin for [Oh My Fish](https://github.com/oh-my-fish/oh-my-fish), which makes nvm and its completions available in fish shell
|
|
|
|
|
- [fnm](https://github.com/fisherman/fnm) - [fisherman](https://github.com/fisherman/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](https://www.freshports.org/www/node/files/patch-deps_v8_src_base_platform_platform-posix.cc); see the issue ticket:
|
|
|
|
|
- [[#900] [Bug] nodejs on FreeBSD may need to be patched ](https://github.com/creationix/nvm/issues/900)
|
|
|
|
|
- [nodejs/node#3716](https://github.com/nodejs/node/issues/3716)
|
|
|
|
|
- [[#900] [Bug] nodejs on FreeBSD may need to be patched ](https://github.com/creationix/nvm/issues/900)
|
|
|
|
|
- [nodejs/node#3716](https://github.com/nodejs/node/issues/3716)
|
|
|
|
|
|
|
|
|
|
**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)](http://osxdaily.com/2014/02/12/install-command-line-tools-mac-os-x/)
|
|
|
|
|
- [How to Install Command Line Tools in OS X Mavericks & Yosemite (Without Xcode)](http://osxdaily.com/2014/02/12/install-command-line-tools-mac-os-x/)
|
|
|
|
|
|
|
|
|
|
**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/*`
|
|
|
|
|
- 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.
|
|
|
|
|
|
|
|
|
|
@ -209,20 +209,20 @@ nvm which 5.0
|
|
|
|
|
|
|
|
|
|
In place of a version pointer like "0.10" or "5.0" or "4.2.1", you can use the following special default aliases with `nvm install`, `nvm use`, `nvm run`, `nvm exec`, `nvm which`, etc:
|
|
|
|
|
|
|
|
|
|
- `node`: this installs the latest version of [`node`](https://nodejs.org/en/)
|
|
|
|
|
- `iojs`: this installs the latest version of [`io.js`](https://iojs.org/en/)
|
|
|
|
|
- `stable`: this alias is deprecated, and only truly applies to `node` `v0.12` and earlier. Currently, this is an alias for `node`.
|
|
|
|
|
- `unstable`: this alias points to `node` `v0.11` - the last "unstable" node release, since post-1.0, all node versions are stable. (in semver, versions communicate breakage, not stability).
|
|
|
|
|
- `node`: this installs the latest version of [`node`](https://nodejs.org/en/)
|
|
|
|
|
- `iojs`: this installs the latest version of [`io.js`](https://iojs.org/en/)
|
|
|
|
|
- `stable`: this alias is deprecated, and only truly applies to `node` `v0.12` and earlier. Currently, this is an alias for `node`.
|
|
|
|
|
- `unstable`: this alias points to `node` `v0.11` - the last "unstable" node release, since post-1.0, all node versions are stable. (in semver, versions communicate breakage, not stability).
|
|
|
|
|
|
|
|
|
|
### Long-term support
|
|
|
|
|
Node has a [schedule](https://github.com/nodejs/LTS#lts_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:
|
|
|
|
|
- `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 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`
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
@ -528,24 +528,24 @@ 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/
|
|
|
|
|
- https://www.docker.com/
|
|
|
|
|
- https://docs.docker.com/
|
|
|
|
|
|
|
|
|
|
## 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:
|
|
|
|
|
- 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](https://github.com/creationix/nvm/issues/43)
|
|
|
|
|
- Where's my `sudo node`? Check out [#43](https://github.com/creationix/nvm/issues/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:
|
|
|
|
|
- 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:
|
|
|
|
|
|
|
|
|
|
```sh
|
|
|
|
|
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](https://github.com/creationix/nvm/issues/658))
|
|
|
|
|
- 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](https://github.com/creationix/nvm/issues/658))
|
|
|
|
|
|
|
|
|
|
## Mac OS "troubleshooting"
|
|
|
|
|
|
|
|
|
|
|
Peter Dave Hello
Jordan Harband