[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-348":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":23,"hasPages":23,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":38,"readmeContent":39,"aiSummary":40,"trendingCount":16,"starSnapshotCount":16,"syncStatus":41,"lastSyncTime":42,"discoverSource":43},348,"nvm","nvm-sh\u002Fnvm","nvm-sh","Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions","",null,"Shell",93826,10227,1066,335,0,9,102,434,45,118,"MIT License",false,"master",[26,27,28,29,30,31,5,32,33,34,35,36,37],"bash","install","lts","node","node-js","nodejs","nvmrc","posix","posix-compliant","shell","version-manager","zsh","2026-06-17 04:00:02","\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Flogos\">\n  \u003Cpicture>\n    \u003Csource media=\"(prefers-color-scheme: dark)\" srcset=\"https:\u002F\u002Fraw.githubusercontent.com\u002Fnvm-sh\u002Flogos\u002FHEAD\u002Fnvm-logo-white.svg\" \u002F>\n    \u003Cimg src=\"https:\u002F\u002Fraw.githubusercontent.com\u002Fnvm-sh\u002Flogos\u002FHEAD\u002Fnvm-logo-color.svg\" height=\"50\" alt=\"nvm project logo\" \u002F>\n  \u003C\u002Fpicture>\n\u003C\u002Fa>\n\n\n# Node Version Manager [![Tests](https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm\u002Factions\u002Fworkflows\u002Ftests-fast.yml\u002Fbadge.svg?branch=master)][3] [![nvm version](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fversion-v0.40.4-yellow.svg)][4] [![CII Best Practices](https:\u002F\u002Fbestpractices.dev\u002Fprojects\u002F684\u002Fbadge)](https:\u002F\u002Fbestpractices.dev\u002Fprojects\u002F684)\n\n\u003C!-- To update this table of contents, ensure you have run `npm install` then `npm run doctoc` -->\n\u003C!-- START doctoc generated TOC please keep comment here to allow auto update -->\n\u003C!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->\n## Table of Contents\n\n- [Intro](#intro)\n- [About](#about)\n- [Installing and Updating](#installing-and-updating)\n  - [Install & Update Script](#install--update-script)\n    - [Additional Notes](#additional-notes)\n    - [Installing in Docker](#installing-in-docker)\n      - [Installing in Docker for CICD-Jobs](#installing-in-docker-for-cicd-jobs)\n    - [Troubleshooting on Linux](#troubleshooting-on-linux)\n    - [Troubleshooting on macOS](#troubleshooting-on-macos)\n    - [Ansible](#ansible)\n  - [Verify Installation](#verify-installation)\n  - [Important Notes](#important-notes)\n  - [Git Install](#git-install)\n  - [Manual Install](#manual-install)\n  - [Manual Upgrade](#manual-upgrade)\n- [Usage](#usage)\n  - [Long-term Support](#long-term-support)\n  - [Migrating Global Packages While Installing](#migrating-global-packages-while-installing)\n  - [Offline Install](#offline-install)\n  - [Default Global Packages From File While Installing](#default-global-packages-from-file-while-installing)\n  - [io.js](#iojs)\n  - [System Version of Node](#system-version-of-node)\n  - [Listing Versions](#listing-versions)\n  - [Setting Custom Colors](#setting-custom-colors)\n    - [Persisting custom colors](#persisting-custom-colors)\n    - [Suppressing colorized output](#suppressing-colorized-output)\n  - [Restoring PATH](#restoring-path)\n  - [Set default node version](#set-default-node-version)\n  - [Use a mirror of node binaries](#use-a-mirror-of-node-binaries)\n    - [Pass Authorization header to mirror](#pass-authorization-header-to-mirror)\n  - [.nvmrc](#nvmrc)\n  - [Deeper Shell Integration](#deeper-shell-integration)\n    - [Calling `nvm use` automatically in a directory with a `.nvmrc` file](#calling-nvm-use-automatically-in-a-directory-with-a-nvmrc-file)\n      - [bash](#bash)\n      - [zsh](#zsh)\n      - [fish](#fish)\n- [Running Tests](#running-tests)\n- [Environment variables](#environment-variables)\n- [Bash Completion](#bash-completion)\n  - [Usage](#usage-1)\n- [Compatibility Issues](#compatibility-issues)\n- [Installing nvm on Alpine Linux](#installing-nvm-on-alpine-linux)\n  - [Alpine Linux 3.13+](#alpine-linux-313)\n  - [Alpine Linux 3.5 - 3.12](#alpine-linux-35---312)\n- [Uninstalling \u002F Removal](#uninstalling--removal)\n  - [Manual Uninstall](#manual-uninstall)\n- [Docker For Development Environment](#docker-for-development-environment)\n- [Problems](#problems)\n- [macOS Troubleshooting](#macos-troubleshooting)\n- [WSL Troubleshooting](#wsl-troubleshooting)\n- [Maintainers](#maintainers)\n- [Project Support](#project-support)\n- [Enterprise Support](#enterprise-support)\n- [License](#license)\n- [Copyright notice](#copyright-notice)\n\n\u003C!-- END doctoc generated TOC please keep comment here to allow auto update -->\n\n## Intro\n\n`nvm` allows you to quickly install and use different versions of node via the command line.\n\n**Example:**\n```sh\n$ nvm install 24\nNow using node v24.14.0 (npm v11.9.0)\n$ node -v\nv24.14.0\n$ nvm use 22\nNow using node v22.22.1 (npm v10.9.4)\n$ node -v\nv22.22.1\n$ nvm use 20\nNow using node v20.20.1 (npm v10.8.2)\n$ node -v\nv20.20.1\n```\n\nSimple as that!\n\n\n## About\nnvm is a version manager for [node.js](https:\u002F\u002Fnodejs.org\u002Fen\u002F), 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](https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm#important-notes).\n\n\u003Ca id=\"installation-and-update\">\u003C\u002Fa>\n\u003Ca id=\"install-script\">\u003C\u002Fa>\n## Installing and Updating\n\n### Install & Update Script\n\nTo **install** or **update** nvm, you should run the [install script][2]. To do that, you may either download and run the script manually, or use the following cURL or Wget command:\n```sh\ncurl -o- https:\u002F\u002Fraw.githubusercontent.com\u002Fnvm-sh\u002Fnvm\u002Fv0.40.4\u002Finstall.sh | bash\n```\n```sh\nwget -qO- https:\u002F\u002Fraw.githubusercontent.com\u002Fnvm-sh\u002Fnvm\u002Fv0.40.4\u002Finstall.sh | bash\n```\n\nRunning either of the above commands downloads a script and runs it. The script clones the nvm repository to `~\u002F.nvm`, and attempts to add the source lines from the snippet below to the correct profile file (`~\u002F.bashrc`, `~\u002F.bash_profile`, `~\u002F.zshrc`, or `~\u002F.profile`). If you find the install script is updating the wrong profile file, set the `$PROFILE` env var to the profile file’s path, and then rerun the installation script.\n\n\u003Ca id=\"profile_snippet\">\u003C\u002Fa>\n```sh\nexport NVM_DIR=\"$([ -z \"${XDG_CONFIG_HOME-}\" ] && printf %s \"${HOME}\u002F.nvm\" || printf %s \"${XDG_CONFIG_HOME}\u002Fnvm\")\"\n[ -s \"$NVM_DIR\u002Fnvm.sh\" ] && \\. \"$NVM_DIR\u002Fnvm.sh\" # This loads nvm\n```\n\n#### Additional Notes\n\n- If the environment variable `$XDG_CONFIG_HOME` is present, it will place the `nvm` files there.\u003C\u002Fsub>\n\n- You can add `--no-use` to the end of the above script to postpone using `nvm` until you manually [`use`](#usage) it:\n\n```sh\nexport NVM_DIR=\"$([ -z \"${XDG_CONFIG_HOME-}\" ] && printf %s \"${HOME}\u002F.nvm\" || printf %s \"${XDG_CONFIG_HOME}\u002Fnvm\")\"\n[ -s \"$NVM_DIR\u002Fnvm.sh\" ] && \\. \"$NVM_DIR\u002Fnvm.sh\" --no-use # This loads nvm, without auto-using the default version\n```\n\n- You can customize the install source, directory, profile, and version using the `NVM_SOURCE`, `NVM_DIR`, `PROFILE`, and `NODE_VERSION` variables.\nEg: `curl ... | NVM_DIR=\"path\u002Fto\u002Fnvm\"`. Ensure that the `NVM_DIR` does not contain a trailing slash.\n\n- The installer can use `git`, `curl`, or `wget` to download `nvm`, whichever is available.\n\n- You can instruct the installer to not edit your shell config (for example if you already get completions via a [zsh nvm plugin](https:\u002F\u002Fgithub.com\u002Fohmyzsh\u002Fohmyzsh\u002Ftree\u002Fmaster\u002Fplugins\u002Fnvm)) by setting `PROFILE=\u002Fdev\u002Fnull` before running the `install.sh` script. Here's an example one-line command to do that: `PROFILE=\u002Fdev\u002Fnull bash -c 'curl -o- https:\u002F\u002Fraw.githubusercontent.com\u002Fnvm-sh\u002Fnvm\u002Fv0.40.4\u002Finstall.sh | bash'`\n\n#### Installing in Docker\n\nWhen invoking bash as a non-interactive shell, like in a Docker container, none of the regular profile files are sourced. In order to use `nvm`, `node`, and `npm` like normal, you can instead specify the special `BASH_ENV` variable, which bash sources when invoked non-interactively.\n\n```Dockerfile\n# Use bash for the shell\nSHELL [\"\u002Fbin\u002Fbash\", \"-o\", \"pipefail\", \"-c\"]\n\n# Create a script file sourced by both interactive and non-interactive bash shells\nENV BASH_ENV \"${HOME}\u002F.bash_env\"\nRUN touch \"${BASH_ENV}\"\nRUN echo '. \"${BASH_ENV}\"' >> ~\u002F.bashrc\n\n# Download and install nvm\nRUN curl -o- https:\u002F\u002Fraw.githubusercontent.com\u002Fnvm-sh\u002Fnvm\u002Fv0.40.4\u002Finstall.sh | PROFILE=\"${BASH_ENV}\" bash\nRUN echo node > .nvmrc\nRUN nvm install\n```\n\n##### Installing in Docker for CICD-Jobs\n\nMore robust, works in CI\u002FCD-Jobs. Can be run in interactive and non-interactive containers.\nSee https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm\u002Fissues\u002F3531.\n\n```Dockerfile\nFROM ubuntu:latest\nARG NODE_VERSION=20\n\n# install curl\nRUN apt update && apt install curl -y\n\n# install nvm\nRUN curl -o- https:\u002F\u002Fraw.githubusercontent.com\u002Fnvm-sh\u002Fnvm\u002Fv0.40.4\u002Finstall.sh | bash\n\n# set env\nENV NVM_DIR=\u002Froot\u002F.nvm\n\n# install node\nRUN bash -c \"source $NVM_DIR\u002Fnvm.sh && nvm install $NODE_VERSION\"\n\n# set ENTRYPOINT for reloading nvm-environment\nENTRYPOINT [\"bash\", \"-c\", \"source $NVM_DIR\u002Fnvm.sh && exec \\\"$@\\\"\", \"--\"]\n\n# set cmd to bash\nCMD [\"\u002Fbin\u002Fbash\"]\n\n```\n\nThis example defaults to installation of nodejs version 20.x.y. Optionally you can easily override the version with docker build args like:\n```\ndocker build -t nvmimage --build-arg NODE_VERSION=19 .\n```\n\nAfter creation of the image you can start container interactively and run commands, for example:\n```\ndocker run --rm -it nvmimage\n\nroot@0a6b5a237c14:\u002F# nvm -v\n0.40.4\n\nroot@0a6b5a237c14:\u002F# node -v\nv19.9.0\n\nroot@0a6b5a237c14:\u002F# npm -v\n9.6.3\n```\n\nNoninteractive example:\n```\nuser@host:\u002Ftmp\u002Ftest $ docker run --rm -it nvmimage node -v\nv19.9.0\nuser@host:\u002Ftmp\u002Ftest $ docker run --rm -it nvmimage npm -v\n9.6.3\n```\n\n#### Troubleshooting on Linux\n\nOn 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.\nAlternatively, you can run the following commands for the different shells on the command line:\n\n*bash*: `source ~\u002F.bashrc`\n\n*zsh*: `source ~\u002F.zshrc`\n\n*ksh*: `. ~\u002F.profile`\n\nThese should pick up the `nvm` command.\n\n#### Troubleshooting on macOS\n\nSince OS X 10.9, `\u002Fusr\u002Fbin\u002Fgit` 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](https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm\u002Fissues\u002F1782))\n\nIf you get `nvm: command not found` after running the install script, one of the following might be the reason:\n\n  - 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 ~\u002F.zshrc` and run the install script again.\n\n  - If you use bash, the previous default shell, your system may not have `.bash_profile` or `.bashrc` files where the command is set up. Create one of them with `touch ~\u002F.bash_profile` or `touch ~\u002F.bashrc` and run the install script again. Then, run `. ~\u002F.bash_profile` or `. ~\u002F.bashrc` to pick up the `nvm` command.\n\n  - You have previously used `bash`, but you have `zsh` installed. You need to manually add [these lines](#manual-install) to `~\u002F.zshrc` and run `. ~\u002F.zshrc`.\n\n  - You might need to restart your terminal instance or run `. ~\u002F.nvm\u002Fnvm.sh`. Restarting your terminal\u002Fopening a new tab\u002Fwindow, or running the source command will load the command and the new configuration.\n\n  - If the above didn't help, you might need to restart your terminal instance. Try opening a new tab\u002Fwindow in your terminal and retry.\n\nIf the above doesn't fix the problem, you may try the following:\n\n  - If you use bash, it may be that your `.bash_profile` (or `~\u002F.profile`) does not source your `~\u002F.bashrc` properly. You could fix this by adding `source ~\u002F\u003Cyour_profile_file>` to it or following the next step below.\n\n  - Try adding [the snippet from the install section](#profile_snippet), that finds the correct nvm directory and loads nvm, to your usual profile (`~\u002F.bash_profile`, `~\u002F.zshrc`, `~\u002F.profile`, or `~\u002F.bashrc`).\n\n  - For more information about this issue and possible workarounds, please [refer here](https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm\u002Fissues\u002F576)\n\n**Note** For Macs with the Apple Silicon chip, node started offering **arm64** arch Darwin packages since v16.0.0 and experimental **arm64** support when compiling from source since v14.17.0. If you are facing issues installing node using `nvm`, you may want to update to one of those versions or later.\n\n#### Ansible\n\nYou can use a task:\n\n```yaml\n- name: Install nvm\n  ansible.builtin.shell: >\n    curl -o- https:\u002F\u002Fraw.githubusercontent.com\u002Fnvm-sh\u002Fnvm\u002Fv0.40.4\u002Finstall.sh | bash\n  args:\n    creates: \"{{ ansible_env.HOME }}\u002F.nvm\u002Fnvm.sh\"\n```\n\n### Verify Installation\n\nTo verify that nvm has been installed, do:\n\n```sh\ncommand -v nvm\n```\n\nwhich 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.\n\n**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.\n\n### Important Notes\n\nIf you're running a system without prepackaged binary available, which means you're going to install node 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\u002FUbuntu based GNU\u002FLinux, the `build-essential` and `libssl-dev` packages work.\n\n**Note:** `nvm` also supports Windows in some cases. It should work through WSL (Windows Subsystem for Linux) depending on the version of WSL. It should also work with [Git Bash](https:\u002F\u002Fgitforwindows.org\u002F) (MSYS) or [Cygwin](https:\u002F\u002Fcygwin.com). Otherwise, for Windows, a few alternatives exist, which are neither supported nor developed by us:\n\n  - [nvm-windows](https:\u002F\u002Fgithub.com\u002Fcoreybutler\u002Fnvm-windows)\n  - [nodist](https:\u002F\u002Fgithub.com\u002Fmarcelklehr\u002Fnodist)\n  - [nvs](https:\u002F\u002Fgithub.com\u002Fjasongin\u002Fnvs)\n\n**Note:** `nvm` does not support [Fish] either (see [#303](https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm\u002Fissues\u002F303)). Alternatives exist, which are neither supported nor developed by us:\n\n  - [bass](https:\u002F\u002Fgithub.com\u002Fedc\u002Fbass) allows you to use utilities written for Bash in fish shell\n  - [fast-nvm-fish](https:\u002F\u002Fgithub.com\u002Fbrigand\u002Ffast-nvm-fish) only works with version numbers (not aliases) but doesn't significantly slow your shell startup\n  - [plugin-nvm](https:\u002F\u002Fgithub.com\u002Fderekstavis\u002Fplugin-nvm) plugin for [Oh My Fish](https:\u002F\u002Fgithub.com\u002Foh-my-fish\u002Foh-my-fish), which makes nvm and its completions available in fish shell\n  - [nvm.fish](https:\u002F\u002Fgithub.com\u002Fjorgebucaran\u002Fnvm.fish) - The Node.js version manager you'll adore, crafted just for Fish\n  - [fish-nvm](https:\u002F\u002Fgithub.com\u002FFabioAntunes\u002Ffish-nvm) - Wrapper around nvm for fish, delays sourcing nvm until it's actually used.\n\n**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:\u002F\u002Fwww.freshports.org\u002Fwww\u002Fnode\u002Ffiles\u002Fpatch-deps_v8_src_base_platform_platform-posix.cc); see the issue ticket:\n\n  - [[#900] [Bug] node on FreeBSD may need to be patched](https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm\u002Fissues\u002F900)\n  - [nodejs\u002Fnode#3716](https:\u002F\u002Fgithub.com\u002Fnodejs\u002Fnode\u002Fissues\u002F3716)\n\n**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:\n\n  - [How to Install Command Line Tools in OS X Mavericks & Yosemite (Without Xcode)](https:\u002F\u002Fosxdaily.com\u002F2014\u002F02\u002F12\u002Finstall-command-line-tools-mac-os-x\u002F)\n\n**Note:** On OS X, if you have\u002Fhad a \"system\" node installed and want to install modules globally, keep in mind that:\n\n  - 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`\n  - If you have an `~\u002F.npmrc` file, make sure it does not contain any `prefix` settings (which is not compatible with `nvm`)\n  - 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 `\u002Fusr\u002Flocal\u002Flib\u002Fnode_modules\u002F*` VS your user account using `~\u002F.nvm\u002Fversions\u002Fnode\u002FvX.X.X\u002Flib\u002Fnode_modules\u002F*`\n\nHomebrew 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.\n\n**Note:** If you're using `zsh` you can easily install `nvm` as a zsh plugin. Install [`zsh-nvm`](https:\u002F\u002Fgithub.com\u002Flukechilds\u002Fzsh-nvm) and run `nvm upgrade` to upgrade ([you can set](https:\u002F\u002Fgithub.com\u002Flukechilds\u002Fzsh-nvm#auto-use) `NVM_AUTO_USE=true` to have it automatically detect and use `.nvmrc` files).\n\n**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](https:\u002F\u002Fgithub.com\u002Fgit\u002Fgit\u002Fcommit\u002F5a7d5b683f869d3e3884a89775241afa515da9e7) 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](https:\u002F\u002Fhelp.github.com\u002Farticles\u002Fhttps-cloning-errors\u002F) article.\n\n### Git Install\n\nIf you have `git` installed (requires git v1.7.10+):\n\n1. clone this repo in the root of your user profile\n    - `cd ~\u002F` from anywhere then `git clone https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm.git .nvm`\n1. `cd ~\u002F.nvm` and check out the latest version with `git checkout v0.40.4`\n1. activate `nvm` by sourcing it from your shell: `. .\u002Fnvm.sh`\n\nNow add these lines to your `~\u002F.bashrc`, `~\u002F.profile`, or `~\u002F.zshrc` file to have it automatically sourced upon login:\n(you may have to add to more than one of the above files)\n\n```sh\nexport NVM_DIR=\"$HOME\u002F.nvm\"\n[ -s \"$NVM_DIR\u002Fnvm.sh\" ] && \\. \"$NVM_DIR\u002Fnvm.sh\"  # This loads nvm\n[ -s \"$NVM_DIR\u002Fbash_completion\" ] && \\. \"$NVM_DIR\u002Fbash_completion\"  # This loads nvm bash_completion\n```\n\n### Manual Install\n\nFor a fully manual install, execute the following lines to first clone the `nvm` repository into `$HOME\u002F.nvm`, and then load `nvm`:\n\n```sh\nexport NVM_DIR=\"$HOME\u002F.nvm\" && (\n  git clone https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm.git \"$NVM_DIR\"\n  cd \"$NVM_DIR\"\n  git checkout `git describe --abbrev=0 --tags --match \"v[0-9]*\" $(git rev-list --tags --max-count=1)`\n) && \\. \"$NVM_DIR\u002Fnvm.sh\"\n```\n\nNow add these lines to your `~\u002F.bashrc`, `~\u002F.profile`, or `~\u002F.zshrc` file to have it automatically sourced upon login:\n(you may have to add to more than one of the above files)\n\n```sh\nexport NVM_DIR=\"$HOME\u002F.nvm\"\n[ -s \"$NVM_DIR\u002Fnvm.sh\" ] && \\. \"$NVM_DIR\u002Fnvm.sh\" # This loads nvm\n[ -s \"$NVM_DIR\u002Fbash_completion\" ] && \\. \"$NVM_DIR\u002Fbash_completion\"  # This loads nvm bash_completion\n```\n\n### Manual Upgrade\n\nFor manual upgrade with `git` (requires git v1.7.10+):\n\n1. change to the `$NVM_DIR`\n1. pull down the latest changes\n1. check out the latest version\n1. activate the new version\n\n```sh\n(\n  cd \"$NVM_DIR\"\n  git fetch --tags origin\n  git checkout `git describe --abbrev=0 --tags --match \"v[0-9]*\" $(git rev-list --tags --max-count=1)`\n) && \\. \"$NVM_DIR\u002Fnvm.sh\"\n```\n\n## Usage\n\nTo download, compile, and install the latest release of node, do this:\n\n```sh\nnvm install node # \"node\" is an alias for the latest version\n```\n\nTo install a specific version of node:\n\n```sh\nnvm install 14.7.0 # or 16.3.0, 12.22.1, etc\n```\n\nTo set an alias:\n\n```sh\nnvm alias my_alias v14.4.0\n```\nMake sure that your alias does not contain any spaces or slashes.\n\nThe first version installed becomes the default. New shells will start with the default version of node (e.g., `nvm alias default`).\n\nYou can list available versions using `ls-remote`:\n\n```sh\nnvm ls-remote\n```\n\nAnd then in any new shell just use the installed version:\n\n```sh\nnvm use node\n```\n\nOr you can just run it:\n\n```sh\nnvm run node --version\n```\n\nOr, you can run any arbitrary command in a subshell with the desired version of node:\n\n```sh\nnvm exec 4.2 node --version\n```\n\nYou can also get the path to the executable to where it was installed:\n\n```sh\nnvm which 12.22\n```\n\nIn place of a version pointer like \"14.7\" or \"16.3\" or \"12.22.1\", you can use the following special default aliases with `nvm install`, `nvm use`, `nvm run`, `nvm exec`, `nvm which`, etc:\n\n  - `node`: this installs the latest version of [`node`](https:\u002F\u002Fnodejs.org\u002Fen\u002F)\n  - `iojs`: this installs the latest version of [`io.js`](https:\u002F\u002Fiojs.org\u002Fen\u002F)\n  - `stable`: this alias is deprecated, and only truly applies to `node` `v0.12` and earlier. Currently, this is an alias for `node`.\n  - `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).\n\n### Long-term Support\n\nNode has a [schedule](https:\u002F\u002Fgithub.com\u002Fnodejs\u002FRelease#release-schedule) for long-term support (LTS) You can reference LTS versions in aliases and `.nvmrc` files with the notation `lts\u002F*` for the latest LTS, and `lts\u002Fargon` for LTS releases from the \"argon\" line, for example. In addition, the following commands support LTS arguments:\n\n  - `nvm install --lts` \u002F `nvm install --lts=argon` \u002F `nvm install 'lts\u002F*'` \u002F `nvm install lts\u002Fargon`\n  - `nvm uninstall --lts` \u002F `nvm uninstall --lts=argon` \u002F `nvm uninstall 'lts\u002F*'` \u002F `nvm uninstall lts\u002Fargon`\n  - `nvm use --lts` \u002F `nvm use --lts=argon` \u002F `nvm use 'lts\u002F*'` \u002F `nvm use lts\u002Fargon`\n  - `nvm exec --lts` \u002F `nvm exec --lts=argon` \u002F `nvm exec 'lts\u002F*'` \u002F `nvm exec lts\u002Fargon`\n  - `nvm run --lts` \u002F `nvm run --lts=argon` \u002F `nvm run 'lts\u002F*'` \u002F `nvm run lts\u002Fargon`\n  - `nvm ls-remote --lts` \u002F `nvm ls-remote --lts=argon` `nvm ls-remote 'lts\u002F*'` \u002F `nvm ls-remote lts\u002Fargon`\n  - `nvm version-remote --lts` \u002F `nvm version-remote --lts=argon` \u002F `nvm version-remote 'lts\u002F*'` \u002F `nvm version-remote lts\u002Fargon`\n\nAny time your local copy of `nvm` connects to https:\u002F\u002Fnodejs.org, it will re-create the appropriate local aliases for all available LTS lines. These aliases (stored under `$NVM_DIR\u002Falias\u002Flts`), 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.\n\nTo get the latest LTS version of node and migrate your existing installed packages, use:\n\n```sh\nnvm install --reinstall-packages-from=current 'lts\u002F*'\n```\n\n### Migrating Global Packages While Installing\n\nIf you want to install a new version of Node.js and migrate npm packages from a previous version:\n\n```sh\nnvm install --reinstall-packages-from=node node\n```\n\nThis 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.\n\nYou can also install and migrate npm packages from specific versions of Node like this:\n\n```sh\nnvm install --reinstall-packages-from=5 6\nnvm install --reinstall-packages-from=iojs v4.2\n```\n\nNote 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.\n\nTo update npm at the same time add the `--latest-npm` flag, like this:\n\n```sh\nnvm install --reinstall-packages-from=default --latest-npm 'lts\u002F*'\n```\n\nor, you can at any time run the following command to get the latest supported npm version on the current node version:\n```sh\nnvm install-latest-npm\n```\n\nIf 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 \u003Cyour latest _working_ version from the ls>`), (2) delete the newly created node version (`nvm uninstall \u003Cyour _broken_ version of node from the ls>`), then (3) rerun your `nvm install` with the `--latest-npm` flag.\n\n\n### Offline Install\n\nIf you've previously downloaded a node version (or it's still in the cache), you can install it without any network access using the `--offline` flag:\n\n```sh\nnvm install --offline 14.7.0\n```\n\nThis resolves versions using only locally installed versions and cached downloads. It will not attempt to download anything. This is useful in air-gapped environments, on planes, or when you want to avoid network latency.\n\nYou can combine `--offline` with `--lts` to install the latest cached LTS version (as long as LTS aliases have been populated by a prior `nvm ls-remote --lts`):\n\n```sh\nnvm install --offline --lts\n```\n\n### Default Global Packages From File While Installing\n\nIf 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\u002Fdefault-packages`. You can add anything npm would accept as a package argument on the command line.\n\n```sh\n# $NVM_DIR\u002Fdefault-packages\n\nrimraf\nobject-inspect@1.0.2\nstevemao\u002Fleft-pad\n```\n\n### io.js\n\n> [!WARNING]\n> io.js was a [fork of Node.js](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FNode.js#History), created in 2014 and merged back in 2015. io.js shipped v1, v2, and v3 release lines; post-merge, node.js began releasing with v4.\n\nIf you want to install io.js:\n\n```sh\nnvm install iojs\n```\n\nIf you want to install a new version of io.js and migrate npm packages from a previous version:\n\n```sh\nnvm install --reinstall-packages-from=iojs iojs\n```\n\nThe same guidelines mentioned for migrating npm packages in node are applicable to io.js.\n\n### System Version of Node\n\nIf you want to use the system-installed version of node, you can use the special default alias \"system\":\n\n```sh\nnvm use system\nnvm run system --version\n```\n\n### Listing Versions\n\nIf you want to see what versions are installed:\n\n```sh\nnvm ls\n```\n\nIf you want to see what versions are available to install:\n\n```sh\nnvm ls-remote\n```\n\n### Setting Custom Colors\n\nYou can set five colors that will be used to display version and alias information. These colors replace the default colors.\n  Initial colors are: g b y r e\n\n  Color codes:\n\n    r\u002FR = red \u002F bold red\n\n    g\u002FG = green \u002F bold green\n\n    b\u002FB = blue \u002F bold blue\n\n    c\u002FC = cyan \u002F bold cyan\n\n    m\u002FM = magenta \u002F bold magenta\n\n    y\u002FY = yellow \u002F bold yellow\n\n    k\u002FK = black \u002F bold black\n\n    e\u002FW = light grey \u002F white\n\n```sh\nnvm set-colors rgBcm\n```\n\n#### Persisting custom colors\n\nIf you want the custom colors to persist after terminating the shell, export the `NVM_COLORS` variable in your shell profile. For example, if you want to use cyan, magenta, green, bold red and bold yellow, add the following line:\n\n```sh\nexport NVM_COLORS='cmgRY'\n```\n\n#### Suppressing colorized output\n\n`nvm help (or -h or --help)`, `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`):\n\n```sh\nnvm ls --no-colors\nnvm help --no-colors\nTERM=dumb nvm ls\n```\n\n### Restoring PATH\nTo restore your PATH, you can deactivate it:\n\n```sh\nnvm deactivate\n```\n\n### Set default node version\nTo set a default Node version to be used in any new shell, use the alias 'default':\n\n```sh\nnvm alias default node # this refers to the latest installed version of node\nnvm alias default 18 # this refers to the latest installed v18.x version of node\nnvm alias default 18.12  # this refers to the latest installed v18.12.x version of node\n```\n\n### Use a mirror of node binaries\nTo use a mirror of the node binaries, set `$NVM_NODEJS_ORG_MIRROR`:\n\n```sh\nexport NVM_NODEJS_ORG_MIRROR=https:\u002F\u002Fnodejs.org\u002Fdist\nnvm install node\n\nNVM_NODEJS_ORG_MIRROR=https:\u002F\u002Fnodejs.org\u002Fdist nvm install 4.2\n```\n\nTo use a mirror of the io.js binaries, set `$NVM_IOJS_ORG_MIRROR`:\n\n```sh\nexport NVM_IOJS_ORG_MIRROR=https:\u002F\u002Fiojs.org\u002Fdist\nnvm install iojs-v1.0.3\n\nNVM_IOJS_ORG_MIRROR=https:\u002F\u002Fiojs.org\u002Fdist nvm install iojs-v1.0.3\n```\n\n`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.\n\n#### Pass Authorization header to mirror\nTo pass an Authorization header through to the mirror url, set `$NVM_AUTH_HEADER`\n\n```sh\nNVM_AUTH_HEADER=\"Bearer secret-token\" nvm install node\n```\n\n### .nvmrc\n\nYou 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).\nAfterwards, `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.\n\nFor example, to make nvm default to the latest 5.9 release, the latest LTS version, or the latest node version for the current directory:\n\n```sh\n$ echo \"5.9\" > .nvmrc\n\n$ echo \"lts\u002F*\" > .nvmrc # to default to the latest LTS version\n\n$ echo \"node\" > .nvmrc # to default to the latest version\n```\n\n[NB these examples assume a POSIX-compliant shell version of `echo`. If you use a Windows `cmd` development environment, eg the `.nvmrc` file is used to configure a remote Linux deployment, then keep in mind the `\"`s will be copied leading to an invalid file. Remove them.]\n\nThen when you run nvm use:\n\n```sh\n$ nvm use\nFound '\u002Fpath\u002Fto\u002Fproject\u002F.nvmrc' with version \u003C5.9>\nNow using node v5.9.1 (npm v3.7.3)\n```\n\nRunning nvm install will also switch over to the correct version, but if the correct node version isn't already installed, it will install it for you.\n\n```sh\n$ nvm install\nFound '\u002Fpath\u002Fto\u002Fproject\u002F.nvmrc' with version \u003C5.9>\nDownloading and installing node v5.9.1...\nDownloading https:\u002F\u002Fnodejs.org\u002Fdist\u002Fv5.9.1\u002Fnode-v5.9.1-linux-x64.tar.xz...\n#################################################################################### 100.0%\nComputing checksum with sha256sum\nChecksums matched!\nNow using node v5.9.1 (npm v3.7.3)\n```\n\n`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.\n\nThe contents of a `.nvmrc` file **must** contain precisely one `\u003Cversion>` (as described by `nvm --help`) followed by a newline. `.nvmrc` files may also have comments. The comment delimiter is `#`, and it and any text after it, as well as blank lines, and leading and trailing white space, will be ignored when parsing.\n\nKey\u002Fvalue pairs using `=` are also allowed and ignored, but are reserved for future use, and may cause validation errors in the future.\n\nRun [`npx nvmrc`](https:\u002F\u002Fnpmjs.com\u002Fnvmrc) to validate an `.nvmrc` file. If that tool’s results do not agree with nvm, one or the other has a bug - please file an issue.\n\n### Deeper Shell Integration\n\nYou can use [`nvshim`](https:\u002F\u002Fgithub.com\u002Fiamogbz\u002Fnvshim) to shim the `node`, `npm`, and `npx` bins to automatically use the `nvm` config in the current directory. `nvshim` is **not** supported by the `nvm` maintainers. Please [report issues to the `nvshim` team](https:\u002F\u002Fgithub.com\u002Fiamogbz\u002Fnvshim\u002Fissues\u002Fnew).\n\nIf you prefer a lighter-weight solution, the recipes below have been contributed by `nvm` users. They are **not** supported by the `nvm` maintainers. We are, however, accepting pull requests for more examples.\n\n#### Calling `nvm use` automatically in a directory with a `.nvmrc` file\n\nIn your profile (`~\u002F.bash_profile`, `~\u002F.zshrc`, `~\u002F.profile`, or `~\u002F.bashrc`), add the following to `nvm use` whenever you enter a new directory:\n\n##### bash\n\nPut the following at the end of your `$HOME\u002F.bashrc`:\n\n```bash\ncdnvm() {\n    command cd \"$@\" || return $?\n    nvm_path=\"$(nvm_find_up .nvmrc | command tr -d '\\n')\"\n\n    # If there are no .nvmrc file, use the default nvm version\n    if [[ ! $nvm_path = *[^[:space:]]* ]]; then\n\n        declare default_version\n        default_version=\"$(nvm version default)\"\n\n        # If there is no default version, set it to `node`\n        # This will use the latest version on your machine\n        if [ $default_version = 'N\u002FA' ]; then\n            nvm alias default node\n            default_version=$(nvm version default)\n        fi\n\n        # If the current version is not the default version, set it to use the default version\n        if [ \"$(nvm current)\" != \"${default_version}\" ]; then\n            nvm use default\n        fi\n    elif [[ -s \"${nvm_path}\u002F.nvmrc\" && -r \"${nvm_path}\u002F.nvmrc\" ]]; then\n        declare nvm_version\n        nvm_version=$(\u003C\"${nvm_path}\"\u002F.nvmrc)\n\n        declare locally_resolved_nvm_version\n        # `nvm ls` will check all locally-available versions\n        # If there are multiple matching versions, take the latest one\n        # Remove the `->` and `*` characters and spaces\n        # `locally_resolved_nvm_version` will be `N\u002FA` if no local versions are found\n        locally_resolved_nvm_version=$(nvm ls --no-colors \"${nvm_version}\" | command tail -1 | command tr -d '\\->*' | command tr -d '[:space:]')\n\n        # If it is not already installed, install it\n        # `nvm install` will implicitly use the newly-installed version\n        if [ \"${locally_resolved_nvm_version}\" = 'N\u002FA' ]; then\n            nvm install \"${nvm_version}\";\n        elif [ \"$(nvm current)\" != \"${locally_resolved_nvm_version}\" ]; then\n            nvm use \"${nvm_version}\";\n        fi\n    fi\n}\n\nalias cd='cdnvm'\ncdnvm \"$PWD\" || exit\n```\n\nThis 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.\n\n##### zsh\n\nThis shell function will install (if needed) and `nvm use` the specified Node version when an `.nvmrc` is found, and `nvm use default` otherwise.\n\nPut this into your `$HOME\u002F.zshrc` to call `nvm use` automatically whenever you enter a directory that contains an\n`.nvmrc` file with a string telling nvm which node to `use`:\n\n```zsh\n# place this after nvm initialization!\nautoload -U add-zsh-hook\n\nload-nvmrc() {\n  local nvmrc_path\n  nvmrc_path=\"$(nvm_find_nvmrc)\"\n\n  if [ -n \"$nvmrc_path\" ]; then\n    local nvmrc_node_version\n    nvmrc_node_version=$(nvm version \"$(cat \"${nvmrc_path}\")\")\n\n    if [ \"$nvmrc_node_version\" = \"N\u002FA\" ]; then\n      nvm install\n    elif [ \"$nvmrc_node_version\" != \"$(nvm version)\" ]; then\n      nvm use\n    fi\n  elif [ -n \"$(PWD=$OLDPWD nvm_find_nvmrc)\" ] && [ \"$(nvm version)\" != \"$(nvm version default)\" ]; then\n    echo \"Reverting to nvm default version\"\n    nvm use default\n  fi\n}\n\nadd-zsh-hook chpwd load-nvmrc\nload-nvmrc\n```\n\nAfter saving the file, run `source ~\u002F.zshrc` to reload the configuration with the latest changes made.\n\n##### fish\n\nThis requires that you have [bass](https:\u002F\u002Fgithub.com\u002Fedc\u002Fbass) installed.\n```fish\n# ~\u002F.config\u002Ffish\u002Ffunctions\u002Fnvm.fish\nfunction nvm\n  bass source ~\u002F.nvm\u002Fnvm.sh --no-use ';' nvm $argv\nend\n\n# ~\u002F.config\u002Ffish\u002Ffunctions\u002Fnvm_find_nvmrc.fish\nfunction nvm_find_nvmrc\n  bass source ~\u002F.nvm\u002Fnvm.sh --no-use ';' nvm_find_nvmrc\nend\n\n# ~\u002F.config\u002Ffish\u002Ffunctions\u002Fload_nvm.fish\nfunction load_nvm --on-variable=\"PWD\"\n  set -l default_node_version (nvm version default)\n  set -l node_version (nvm version)\n  set -l nvmrc_path (nvm_find_nvmrc)\n  if test -n \"$nvmrc_path\"\n    set -l nvmrc_node_version (nvm version (cat $nvmrc_path))\n    if test \"$nvmrc_node_version\" = \"N\u002FA\"\n      nvm install (cat $nvmrc_path)\n    else if test \"$nvmrc_node_version\" != \"$node_version\"\n      nvm use $nvmrc_node_version\n    end\n  else if test \"$node_version\" != \"$default_node_version\"\n    echo \"Reverting to default Node version\"\n    nvm use default\n  end\nend\n\n# ~\u002F.config\u002Ffish\u002Fconfig.fish\n# You must call it on initialization or listening to directory switching won't work\nload_nvm > \u002Fdev\u002Fstderr\n```\n\n## Running Tests\n\nTests are written in [Urchin]. Install Urchin (and other dependencies) like so:\n\n    npm install\n\nThere are slow tests and fast tests. The slow tests do things like install node\nand check that the right versions are used. The fast tests fake this to test\nthings like aliases and uninstalling. From the root of the nvm git repository,\nrun the fast tests like this:\n\n    npm run test\u002Ffast\n\nRun the slow tests like this:\n\n    npm run test\u002Fslow\n\nRun all of the tests like this:\n\n    npm test\n\nNota bene: Avoid running nvm while the tests are running.\n\n## Environment variables\n\nnvm exposes the following environment variables:\n\n- `NVM_DIR` - nvm's installation directory.\n- `NVM_BIN` - where node, npm, and global packages for the active version of node are installed.\n- `NVM_INC` - node's include file directory (useful for building C\u002FC++ addons for node).\n- `NVM_CD_FLAGS` - used to maintain compatibility with zsh.\n- `NVM_RC_VERSION` - version from .nvmrc file if being used.\n\nAdditionally, nvm modifies `PATH`, and, if present, `MANPATH` and `NODE_PATH` when changing versions.\n\n\n## Bash Completion\n\nTo activate, you need to source `bash_completion`:\n\n```sh\n[[ -r $NVM_DIR\u002Fbash_completion ]] && \\. $NVM_DIR\u002Fbash_completion\n```\n\nPut the above sourcing line just below the sourcing line for nvm in your profile (`.bashrc`, `.bash_profile`).\n\n### Usage\n\nnvm:\n\n> `$ nvm` \u003Ckbd>Tab\u003C\u002Fkbd>\n```sh\nalias               deactivate          install             list-remote         reinstall-packages  uninstall           version\ncache               exec                install-latest-npm  ls                  run                 unload              version-remote\ncurrent             help                list                ls-remote           unalias             use                 which\n```\n\nnvm alias:\n\n> `$ nvm alias` \u003Ckbd>Tab\u003C\u002Fkbd>\n```sh\ndefault      iojs         lts\u002F*        lts\u002Fargon    lts\u002Fboron    lts\u002Fcarbon   lts\u002Fdubnium  lts\u002Ferbium   node         stable       unstable\n```\n\n\n> `$ nvm alias my_alias` \u003Ckbd>Tab\u003C\u002Fkbd>\n```sh\nv10.22.0       v12.18.3      v14.8.0\n```\n\nnvm use:\n> `$ nvm use` \u003Ckbd>Tab\u003C\u002Fkbd>\n\n```\nmy_alias        default        v10.22.0       v12.18.3      v14.8.0\n```\n\nnvm uninstall:\n> `$ nvm uninstall` \u003Ckbd>Tab\u003C\u002Fkbd>\n\n```\nmy_alias        default        v10.22.0       v12.18.3      v14.8.0\n```\n\n## Compatibility Issues\n\n`nvm` will encounter some issues if you have some non-default settings set. (see [#606](https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm\u002Fissues\u002F606))\nThe following are known to cause issues:\n\nInside `~\u002F.npmrc`:\n\n```sh\nprefix='some\u002Fpath'\n```\n\nEnvironment Variables:\n\n```sh\n$NPM_CONFIG_PREFIX\n$PREFIX\n```\n\nShell settings:\n\n```sh\nset -e\n```\n\n## Installing nvm on Alpine Linux\n\nIn order to provide the best performance (and other optimizations), 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\u002Fprovides these pre-compiled binaries which are built for mainstream\u002Ftraditional Linux distributions (such as Debian, Ubuntu, CentOS, RedHat et al).\n\nAlpine Linux, unlike mainstream\u002Ftraditional Linux distributions, is based on [BusyBox](https:\u002F\u002Fwww.busybox.net\u002F), a very compact (~5MB) Linux distribution. BusyBox (and thus Alpine Linux) uses a different C\u002FC++ stack to most mainstream\u002Ftraditional Linux distributions - [musl](https:\u002F\u002Fwww.musl-libc.org\u002F). This makes binary programs built for such mainstream\u002Ftraditional 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.\n\nThere is a `-s` flag for `nvm install` which requests nvm download Node source and compile it locally.\n\nIf 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 your Alpine Linux shell, depending on which version you are using:\n\n### Alpine Linux 3.13+\n```sh\napk add -U curl bash ca-certificates openssl ncurses coreutils python3 make gcc g++ libgcc linux-headers grep util-linux binutils findutils\ncurl -o- https:\u002F\u002Fraw.githubusercontent.com\u002Fnvm-sh\u002Fnvm\u002Fv0.40.4\u002Finstall.sh | bash\n```\n\n### Alpine Linux 3.5 - 3.12\n```sh\napk add -U curl bash ca-certificates openssl ncurses coreutils python2 make gcc g++ libgcc linux-headers grep util-linux binutils findutils\ncurl -o- https:\u002F\u002Fraw.githubusercontent.com\u002Fnvm-sh\u002Fnvm\u002Fv0.40.4\u002Finstall.sh | bash\n```\n\n_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` to build NodeJS, as they are older versions to build. Alpine 3.13+ requires `python3` to successfully build newer NodeJS versions, but you can use `python2` with Alpine 3.13+ if you need to build versions of node supported in Alpine 3.5 - 3.15, you just need to specify what version of NodeJS you need to install in the package install script._\n\nThe Node project has some desire but no concrete plans (due to the overheads of building, testing and support) to offer Alpine-compatible binaries.\n\nAs a potential alternative, @mhart (a Node contributor) has some [Docker images for Alpine Linux with Node and optionally, npm, pre-installed](https:\u002F\u002Fgithub.com\u002Fmhart\u002Falpine-node).\n\n\u003Ca id=\"removal\">\u003C\u002Fa>\n## Uninstalling \u002F Removal\n\n### Manual Uninstall\n\nTo remove `nvm` manually, execute the following:\n\nFirst, use `nvm unload` to remove the nvm command from your terminal session and delete the installation directory:\n\n```sh\n$ nvm_dir=\"${NVM_DIR:-~\u002F.nvm}\"\n$ nvm unload\n$ rm -rf \"$nvm_dir\"\n```\n\nEdit `~\u002F.bashrc` (or other shell resource config) and remove the lines below:\n\n```sh\nexport NVM_DIR=\"$HOME\u002F.nvm\"\n[ -s \"$NVM_DIR\u002Fnvm.sh\" ] && \\. \"$NVM_DIR\u002Fnvm.sh\" # This loads nvm\n[[ -r $NVM_DIR\u002Fbash_completion ]] && \\. $NVM_DIR\u002Fbash_completion\n```\n\n## Docker For Development Environment\n\nTo 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 `nvm` development, to build the docker image of the environment, run the docker command at the root of `nvm` repository:\n\n```sh\n$ docker build -t nvm-dev .\n```\n\nThis 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`:\n\n```sh\n$ docker images\n\nREPOSITORY         TAG                 IMAGE ID            CREATED             SIZE\nnvm-dev            latest              9ca4c57a97d8        7 days ago          650 MB\n```\n\nIf you got no error message, now you can easily involve in:\n\n```sh\n$ docker run -h nvm-dev -it nvm-dev\n\nnvm@nvm-dev:~\u002F.nvm$\n```\n\nPlease 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.\n\nFor more information and documentation about docker, please refer to its official website:\n\n  - https:\u002F\u002Fwww.docker.com\u002F\n  - https:\u002F\u002Fdocs.docker.com\u002F\n\n## Problems\n\n  - 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:\n\n    curl: (33) HTTP server doesn't seem to support byte ranges. Cannot resume.\n\n  - Where's my `sudo node`? Check out [#43](https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm\u002Fissues\u002F43)\n\n  - 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:\n\n```sh\nnvm install -s 0.8.6\n```\n\n  - 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:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm\u002Fissues\u002F658))\n\n## macOS Troubleshooting\n\n**nvm node version not found in vim shell**\n\nIf 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:\n\n```shell\nsudo chmod ugo-x \u002Fusr\u002Flibexec\u002Fpath_helper\n```\n\nMore on this issue in [dotphiles\u002Fdotzsh](https:\u002F\u002Fgithub.com\u002Fdotphiles\u002Fdotzsh#mac-os-x).\n\n**nvm is not compatible with the npm config \"prefix\" option**\n\nSome solutions for this issue can be found [here](https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm\u002Fissues\u002F1245)\n\nThere is one more edge case causing this issue, and that's a **mismatch between the `$HOME` path and the user's home directory's actual name**.\n\nYou have to make sure that the user directory name in `$HOME` and the user directory name you'd see from running `ls \u002FUsers\u002F` **are capitalized the same way** ([See this issue](https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm\u002Fissues\u002F2261)).\n\nTo change the user directory and\u002For account name follow the instructions [here](https:\u002F\u002Fsupport.apple.com\u002Fen-us\u002FHT201548)\n\n[1]: https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm.git\n[2]: https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm\u002Fblob\u002Fv0.40.4\u002Finstall.sh\n[3]: https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm\u002Factions\u002Fworkflows\u002Ftests-fast.yml\n[4]: https:\u002F\u002Fgithub.com\u002Fnvm-sh\u002Fnvm\u002Freleases\u002Ftag\u002Fv0.40.4\n[Urchin]: https:\u002F\u002Fgit.sdf.org\u002Ftlevine\u002Furchin\n[Fish]: https:\u002F\u002Ffishshell.com\n\n**Homebrew makes zsh directories insecure**\n\n```shell\nzsh compinit: insecure directories, run compaudit for list.\nIgnore insecure directories and continue [y] or abort compinit [n]? y\n```\n\nHomebrew causes insecure directories like `\u002Fusr\u002Flocal\u002Fshare\u002Fzsh\u002Fsite-functions` and `\u002Fusr\u002Flocal\u002Fshare\u002Fzsh`. This is **not** an `nvm` problem - it is a homebrew problem. Refer [here](https:\u002F\u002Fgithub.com\u002Fzsh-users\u002Fzsh-completions\u002Fissues\u002F680) for some solutions related to the issue.\n\n**Macs with Apple Silicon chips**\n\nExperimental support for the Apple Silicon chip architecture was added in node.js v15.3 and full support was added in v16.0.\nBecause 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.\n\nSo, if you want to run a version prior to v16.0 on an Apple Silicon Mac, it may be best to compile node targeting the `x86_64` Intel architecture so that Rosetta 2 can translate the `x86_64` processor instructions to ARM-based Apple Silicon instructions.\nHere's what you will need to do:\n\n- Install Rosetta, if you haven't already done so\n\n  ```sh\n  $ softwareupdate --install-rosetta\n  ```\n\n  You might wonder, \"how will my Apple Silicon Mac know to use Rosetta for a version of node compiled for an Intel chip?\".\n  If an executable contains only Intel instructions, macOS will automatically use Rosetta to translate the instructions.\n\n- Open a shell that's running using Rosetta\n\n  ```sh\n  $ arch -x86_64 zsh\n  ```\n\n  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\".\n\n  Note: This terminal session is now running in `zsh`.\n  If `zsh` is not the shell you typically use, `nvm` may not be `source`'d automatically like it probably is for your usual shell through your dotfiles.\n  If that's the case, make sure to source `nvm`.\n\n  ```sh\n  $ source \"${NVM_DIR}\u002Fnvm.sh\"\n  ```\n\n- Install whatever older version of node you are interested in. Let's use 12.22.1 as an example.\n  This will fetch the node source code and compile it, which will take several minutes.\n\n  ```sh\n  $ nvm install v12.22.1 --shared-zlib\n  ```\n\n  Note: You're probably curious why `--shared-zlib` is included.\n  There's a bug in recent versions of Apple's system `clang` compiler.\n  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 `--shared-zlib` flag.\n  However, later, when you attempt to `npm install` something using your old version of node.js, you will see `incorrect data check` errors.\n  If you want to avoid the possible hassle of dealing with this, include that flag.\n  For more details, see [this issue](https:\u002F\u002Fgithub.com\u002Fnodejs\u002Fnode\u002Fissues\u002F39313) and [this comment](https:\u002F\u002Fgithub.com\u002Fnodejs\u002Fnode\u002Fissues\u002F39313#issuecomment-90.40.476)\n\n- Exit back to your native shell.\n\n  ```sh\n  $ exit\n  $ arch\n  arm64\n  ```\n\n  Note: If you selected the box labeled \"Open using Rosetta\" rather than running the CLI command in the second step, you will see `i386` here.\n  Unless you have another reason to have that box selected, you can deselect it now.\n\n- Check to make sure the architecture is correct. `x64` is the abbreviation for `x86_64`, which is what you want to see.\n\n  ```sh\n  $ node -p process.arch\n  x64\n  ```\n\nNow you should be able to use node as usual.\n\n## WSL Troubleshooting\n\nIf you've encountered this error on WSL-2:\n\n  ```sh\n  curl -o- https:\u002F\u002Fraw.githubusercontent.com\u002Fnvm-sh\u002Fnvm\u002Fv0.40.4\u002Finstall.sh | bash\n  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current\n                                  Dload  Upload  Total   Spent    Left  Speed\n  0     0    0     0    0     0      0      0 --:--:--  0:00:09 --:--:--     0curl: (6) Could not resolve host: raw.githubusercontent.com\n  ```\n\nIt may be due to your antivirus, VPN, or other reasons.\n\nWhere you can `ping 8.8.8.8` while you can't `ping google.com`\n\n\nThis could simply be solved by running this in your root directory:\n\n  ```sh\n  sudo rm \u002Fetc\u002Fresolv.conf\n  sudo bash -c 'echo \"nameserver 8.8.8.8\" > \u002Fetc\u002Fresolv.conf'\n  sudo bash -c 'echo \"[network]\" > \u002Fetc\u002Fwsl.conf'\n  sudo bash -c 'echo \"generateResolvConf = false\" >> \u002Fetc\u002Fwsl.conf'\n  sudo chattr +i \u002Fetc\u002Fresolv.conf\n  ```\n\nThis deletes your `resolv.conf` file that is automatically generated when you run WSL, creates a new file and puts `nameserver 8.8.8.8`, then creates a `wsl.conf` file and adds `[network]` and `generateResolveConf = false` to prevent auto-generation of that file.\n\nYou can check the contents of the file by running:\n\n  ```sh\n  cat \u002Fetc\u002Fresolv.conf\n  ```\n\n## Maintainers\n\nCurrently, the sole maintainer is [@ljharb](https:\u002F\u002Fgithub.com\u002Fljharb) - more maintainers are quite welcome, and we hope to add folks to the team over time. [Governance](.\u002FGOVERNANCE.md) will be re-evaluated as the project evolves.\n\n## Project Support\n\nOnly the latest version (v0.40.4 at this time) is supported.\n\n## Enterprise Support\n\nIf you are unable to update to the latest version of `nvm`, our [partners](https:\u002F\u002Fopenjsf.org\u002Fecosystem-sustainability-program) provide commercial security fixes for all unsupported versions:\n\n  - [HeroDevs Never-Ending Support](https:\u002F\u002Fwww.herodevs.com\u002Fsupport?utm_source=OpenJS&utm_medium=Link&utm_campaign=nvm_openjs)\n\n## License\n\nSee [LICENSE.md](.\u002FLICENSE.md).\n\n## Copyright notice\n\nCopyright [OpenJS Foundation](https:\u002F\u002Fopenjsf.org) and `nvm` contributors. All rights reserved. The [OpenJS Foundation](https:\u002F\u002Fopenjsf.org) has registered trademarks and uses trademarks.  For a list of trademarks of the [OpenJS Foundation](https:\u002F\u002Fopenjsf.org), please see our [Trademark Policy](https:\u002F\u002Ftrademark-policy.openjsf.org\u002F) and [Trademark List](https:\u002F\u002Ftrademark-list.openjsf.org\u002F).  Trademarks and logos not indicated on the [list of OpenJS Foundation trademarks](https:\u002F\u002Ftrademark-list.openjsf.org) are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.\n[The OpenJS Foundation](https:\u002F\u002Fopenjsf.org\u002F) | [Terms of Use](https:\u002F\u002Fterms-of-use.openjsf.org\u002F) | [Privacy Policy](https:\u002F\u002Fprivacy-policy.openjsf.org\u002F) | [Bylaws](https:\u002F\u002Fbylaws.openjsf.org\u002F) | [Code of Conduct](https:\u002F\u002Fcode-of-conduct.openjsf.org) | [Trademark Policy](https:\u002F\u002Ftrademark-policy.openjsf.org\u002F) | [Trademark List](https:\u002F\u002Ftrademark-list.openjsf.org\u002F) | [Cookie Policy](https:\u002F\u002Fwww.linuxfoundation.org\u002Fcookies\u002F)\n","nvm 是一个用于管理多个 Node.js 版本的 POSIX 兼容 Bash 脚本。其核心功能包括安装、切换和卸载不同版本的 Node.js，支持通过 `.nvmrc` 文件自动设置项目所需的 Node.js 版本，并且可以轻松迁移全局包。nvm 采用 Shell 编写，具有良好的跨平台兼容性，适用于 Linux 和 macOS 等系统。它特别适合需要在不同项目中使用不同 Node.js 版本的开发者，以及希望简化 Node.js 环境配置和管理的团队。",2,"2026-06-17 02:34:23","top_all"]