Github url

nvm

by nvm-sh

nvm-sh /nvm

Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions

43.2K Stars 4.2K Forks Last release: 5 months ago (v0.35.3) MIT License 1.9K Commits 85 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

Node Version Manager Build Status nvm version CII Best Practices

Table of Contents

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.

Installing and Updating

Install & Update Script

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:

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

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 (

~/.bash\_profile

,

~/.zshrc

,

~/.profile

, or

~/.bashrc

).

sh export NVM\_DIR="$([-z "${XDG\_CONFIG\_HOME-}"] && printf %s "${HOME}/.nvm" || printf %s "${XDG\_CONFIG\_HOME}/nvm")" [-s "$NVM\_DIR/nvm.sh"] && \. "$NVM\_DIR/nvm.sh" # This loads nvm

Additional Notes

  • If the environment variable

$XDG\_CONFIG\_HOME

is present, it will place the

nvm

files there.

You can add

--no-use

to the end of the above script (...

nvm.sh --no-use

) to postpone using

nvm

until you manually [

use

](https://github.com/nvm-sh/nvm/blob/master/#usage) it.

You can customize the install source, directory, profile, and version using the

NVM\_SOURCE

,

NVM\_DIR

,

PROFILE

, and

NODE\_VERSION

variables. Eg:

curl ... | NVM\_DIR="path/to/nvm"

. Ensure that the

NVM\_DIR

does not contain a trailing slash.

The installer can use

git

,

curl

, or

wget

to download

nvm

, whichever is available.

Troubleshooting on Linux

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.

Troubleshooting on macOS

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)

If you get

nvm: command not found

after running the install script, one of the following might be the reason:

Since macOS 10.15, the default shell is

zsh

and nvm will look for

.zshrc

to update, none is installed by default. Create one with

touch ~/.zshrc

and run the install script again.

If you use bash, the previous default shell, run

touch ~/.bash\_profile

to create the necessary profile file if it does not exist.

You might need to restart your terminal instance or run

. ~/.nvm/nvm.sh

. Restarting your terminal/opening a new tab/window, or running the source command will load the command and the new configuration.

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

  • If you use bash, it may be that your

.bash\_profile

(or

~/.profile

) does not source your

~/.bashrc

properly. You could fix this by adding

source ~/<your_profile_file></your_profile_file>

to it or follow the next step below.

Try adding the snippet from the install section, that finds the correct nvm directory and loads nvm, to your usual profile (

~/.bash\_profile

,

~/.zshrc

,

~/.profile

, or

~/.bashrc

).

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

Ansible

You can use a task:

- name: nvm shell: \> curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | bash args: creates: "{{ ansible\_env.HOME }}/.nvm/nvm.sh"

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.

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), but may work in WSL (Windows Subsystem for Linux) depending on the version of WSL. For Windows, 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
  • fish-nvm - Wrapper around nvm for fish, delays sourcing nvm until it's actually used.

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:

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

](https://github.com/lukechilds/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, 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.

Git Install

If you have

git

installed (requires git v1.7.10+):

  1. clone this repo in the root of your user profile

    cd ~/
    from anywhere then
    git clone https://github.com/nvm-sh/nvm.git .nvm
  2. cd ~/.nvm
    and check out the latest version with
    git checkout v0.35.3
  3. 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

Manual Install

For a fully manual install, execute the following lines to first clone the

nvm

repository into

$HOME/.nvm

, and then load

nvm

:

export NVM\_DIR="$HOME/.nvm" && ( git clone https://github.com/nvm-sh/nvm.git "$NVM\_DIR" cd "$NVM\_DIR" git checkout `git describe --abbrev=0 --tags --match "v[0-9]*" $(git rev-list --tags --max-count=1)` ) && \. "$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

Manual Upgrade

For manual upgrade with

git

(requires git v1.7.10+):

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

Usage

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

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

To install a specific version of node:

nvm install 6.14.4 # or 10.10.0, 8.9.1, etc

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

nvm alias default

).

You can list available versions using

ls-remote

:

nvm ls-remote

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

nvm use node

Or you can just run it:

nvm run node --version

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

nvm exec 4.2 node --version

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

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

Long-term Support

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:

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.

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

nvm install --lts --reinstall-packages-from=current

Migrating Global Packages While Installing

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

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

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.

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

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

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.

To update npm at the same time add the

--latest-npm

flag, like this:

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

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

sh nvm install-latest-npm

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></your>

, (2) delete the newly created node version (

nvm uninstall <your _broken_ version of node from the ls></your>

), then (3) rerun your

nvm install

with the

--latest-npm

flag.

Default Global Packages From File While Installing

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.

# $NVM\_DIR/default-packages rimraf [email protected] stevemao/left-pad

io.js

If you want to install io.js:

nvm install iojs

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

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

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

System Version of Node

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

nvm use system nvm run system --version

Listing Versions

If you want to see what versions are installed:

nvm ls

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

nvm ls-remote

Suppressing colorized output

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

):

nvm ls --no-colors TERM=dumb nvm ls

To restore your PATH, you can deactivate it:

nvm deactivate

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

nvm alias default node

To use a mirror of the node binaries, set

$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

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

$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

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.

.nvmrc

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

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.

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:

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

Then when you run nvm:

$ nvm use Found '/path/to/project/.nvmrc' with version \<5.9\> Now using node v5.9.1 (npm v3.7.3)
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.

The contents of a

.nvmrc

file must be the

<version></version>

(as described by

nvm --help

) followed by a newline. No trailing spaces are allowed, and the trailing newline is required.

Deeper Shell Integration

You can use [

avn

](https://github.com/wbyoung/avn) to deeply integrate into your shell and automatically invoke

nvm

when changing directories.

avn

is not supported by the

nvm

development team. Please [report issues to the

avn

team](https://github.com/wbyoung/avn/issues/new).

If you prefer a lighter-weight solution, the recipes below have been contributed by

nvm

users. They are not supported by the

nvm

development team. We are, however, accepting pull requests for more examples.

bash

Automatically call
nvm use

Put the following at the end of your

$HOME/.bashrc

:

find-up () { path=$(pwd) while [["$path" != "" && ! -e "$path/$1"]]; do path=${path%/\*} done echo "$path" } cdnvm(){ cd "[email protected]"; nvm\_path=$(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=$(` 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'

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.

zsh

Calling
nvm use

automatically in a directory with a

.nvmrc

file

Put this into your

$HOME/.zshrc

to call

nvm use

automatically whenever you enter a directory that contains an

.nvmrc

file with a string telling nvm which node to

use

:

# place this after nvm initialization! 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

fish

Calling
nvm use

automatically in a directory with a

.nvmrc

file

This requires that you have bass installed. ```fish

~/.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 ```

License

nvm is released under the MIT license.

Copyright (C) 2010 Tim Caswell and Jordan Harband

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.

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

PATH

, and, if present,

MANPATH

and

NODE\_PATH

when changing versions.

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

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

Installing nvm on Alpine Linux

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 these pre-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/nvm-sh/nvm/v0.35.3/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.

Uninstalling / Removal

Manual Uninstall

To remove

nvm

manually, execute the following:

$ rm -rf "$NVM\_DIR"

Edit

~/.bashrc

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

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 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-defined 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 650 MB

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

$ docker run -h nvm-dev -it nvm-dev [email protected]:~/.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:

Problems

  • If you try to install a node version and the installation fails, be sure to run

nvm cache clear

to delete cached node downloads, 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)

macOS 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

More on this issue in dotphiles/dotzsh.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.