[{"_1":2,"_161":-5,"_162":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_140":141},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_88":-5,"_89":90,"_129":-5,"_130":11,"_131":21,"_132":11,"_133":-5,"_134":11,"_135":-5,"_136":137,"_138":91,"_139":-7},"canonicalUrl","https://hub.docker.com/r/hzgood/docker-nvm-dev/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","hzgood","reponame","docker-nvm-dev","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_42":43,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":55,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":74,"_79":11,"_80":81,"_85":33,"_86":87},"categories",[],"content_types",[44],"image","date_registered","2020-12-06T14:17:30.518084Z","description","a image for nvm-dev","is_private","last_updated","2020-12-06T14:24:25.858732Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[56],"application/vnd.docker.container.image.v1+json","name","pull_count",1029,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# Node Version Manager [![Build Status](https://travis-ci.org/nvm-sh/nvm.svg?branch=master)][3] [![nvm version](https://img.shields.io/badge/version-v0.37.2-yellow.svg)][4] [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/684/badge)](https://bestpractices.coreinfrastructure.org/projects/684)\n\n\n\n\n## Table of Contents\n\n- [About](#about)\n- [Installing and Updating](#installing-and-updating)\n - [Install & Update Script](#install--update-script)\n - [Additional Notes](#additional-notes)\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 - [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 - [.nvmrc](#nvmrc)\n - [Deeper Shell Integration](#deeper-shell-integration)\n - [bash](#bash)\n - [Automatically call `nvm use`](#automatically-call-nvm-use)\n - [zsh](#zsh)\n - [Calling `nvm use` automatically in a directory with a `.nvmrc` file](#calling-nvm-use-automatically-in-a-directory-with-a-nvmrc-file)\n - [fish](#fish)\n - [Calling `nvm use` automatically in a directory with a `.nvmrc` file](#calling-nvm-use-automatically-in-a-directory-with-a-nvmrc-file-1)\n- [License](#license)\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- [Uninstalling / 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\n\n\n## About\nnvm is a version manager for [node.js](https://nodejs.org/en/), 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.\n\n\n\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://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash\n```\n```sh\nwget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash\n```\n\nRunning 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`).\n\n\n```sh\nexport NVM_DIR=\"$([ -z \"${XDG_CONFIG_HOME-}\" ] && printf %s \"${HOME}/.nvm\" || printf %s \"${XDG_CONFIG_HOME}/nvm\")\"\n[ -s \"$NVM_DIR/nvm.sh\" ] && \\. \"$NVM_DIR/nvm.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.\n\n- You can add `--no-use` to the end of the above script (...`nvm.sh --no-use`) to postpone using `nvm` until you manually [`use`](#usage) it.\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/to/nvm\"`. 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#### 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.\n\n#### Troubleshooting on macOS\n\nSince 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](https://github.com/nvm-sh/nvm/issues/1782))\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 ~/.zshrc` and run the install script again.\n\n - If you use bash, the previous default shell, run `touch ~/.bash_profile` to create the necessary profile file if it does not exist.\n\n - 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.\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 `~/.profile`) does not source your `~/.bashrc` properly. You could fix this by adding `source ~/` to it or follow 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 (`~/.bash_profile`, `~/.zshrc`, `~/.profile`, or `~/.bashrc`).\n\n - For more information about this issue and possible workarounds, please [refer here](https://github.com/nvm-sh/nvm/issues/576)\n\n#### Ansible\n\nYou can use a task:\n\n```yaml\n- name: nvm\n shell: >\n curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash\n args:\n creates: \"{{ ansible_env.HOME }}/.nvm/nvm.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### Important Notes\n\nIf 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.\n\n**Note:** `nvm` does not support Windows (see [#284](https://github.com/nvm-sh/nvm/issues/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:\n\n - [nvm-windows](https://github.com/coreybutler/nvm-windows)\n - [nodist](https://github.com/marcelklehr/nodist)\n\n**Note:** `nvm` does not support [Fish] either (see [#303](https://github.com/nvm-sh/nvm/issues/303)). Alternatives exist, which are neither supported nor developed by us:\n\n - [bass](https://github.com/edc/bass) allows you to use utilities written for Bash in fish shell\n - [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\n - [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\n - [fnm](https://github.com/fisherman/fnm) - [fisherman](https://github.com/fisherman/fisherman)-based version manager for fish\n - [fish-nvm](https://github.com/FabioAntunes/fish-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://www.freshports.org/www/node/files/patch-deps_v8_src_base_platform_platform-posix.cc); see the issue ticket:\n\n - [[#900] [Bug] nodejs on FreeBSD may need to be patched](https://github.com/nvm-sh/nvm/issues/900)\n - [nodejs/node#3716](https://github.com/nodejs/node/issues/3716)\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)](http://osxdaily.com/2014/02/12/install-command-line-tools-mac-os-x/)\n\n**Note:** On OS X, if you have/had 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 `~/.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 `/usr/local/lib/node_modules/*` VS your user account using `~/.nvm/versions/node/vX.X.X/lib/node_modules/*`\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://github.com/lukechilds/zsh-nvm) and run `nvm upgrade` to upgrade.\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://github.com/git/git/commit/5a7d5b683f869d3e3884a89775241afa515da9e7) 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://help.github.com/articles/https-cloning-errors/) 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 ~/` from anywhere then `git clone https://github.com/nvm-sh/nvm.git .nvm`\n1. `cd ~/.nvm` and check out the latest version with `git checkout v0.37.2`\n1. activate `nvm` by sourcing it from your shell: `. nvm.sh`\n\nNow add these lines to your `~/.bashrc`, `~/.profile`, or `~/.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/.nvm\"\n[ -s \"$NVM_DIR/nvm.sh\" ] && \\. \"$NVM_DIR/nvm.sh\" # This loads nvm\n[ -s \"$NVM_DIR/bash_completion\" ] && \\. \"$NVM_DIR/bash_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/.nvm`, and then load `nvm`:\n\n```sh\nexport NVM_DIR=\"$HOME/.nvm\" && (\n git clone https://github.com/nvm-sh/nvm.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/nvm.sh\"\n```\n\nNow add these lines to your `~/.bashrc`, `~/.profile`, or `~/.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/.nvm\"\n[ -s \"$NVM_DIR/nvm.sh\" ] && \\. \"$NVM_DIR/nvm.sh\" # This loads nvm\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/nvm.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 6.14.4 # or 10.10.0, 8.9.1, etc\n```\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 5.0\n```\n\nIn 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:\n\n - `node`: this installs the latest version of [`node`](https://nodejs.org/en/)\n - `iojs`: this installs the latest version of [`io.js`](https://iojs.org/en/)\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://github.com/nodejs/Release#release-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:\n\n - `nvm install --lts` / `nvm install --lts=argon` / `nvm install 'lts/*'` / `nvm install lts/argon`\n - `nvm uninstall --lts` / `nvm uninstall --lts=argon` / `nvm uninstall 'lts/*'` / `nvm uninstall lts/argon`\n - `nvm use --lts` / `nvm use --lts=argon` / `nvm use 'lts/*'` / `nvm use lts/argon`\n - `nvm exec --lts` / `nvm exec --lts=argon` / `nvm exec 'lts/*'` / `nvm exec lts/argon`\n - `nvm run --lts` / `nvm run --lts=argon` / `nvm run 'lts/*'` / `nvm run lts/argon`\n - `nvm ls-remote --lts` / `nvm ls-remote --lts=argon` `nvm ls-remote 'lts/*'` / `nvm ls-remote lts/argon`\n - `nvm version-remote --lts` / `nvm version-remote --lts=argon` / `nvm version-remote 'lts/*'` / `nvm version-remote lts/argon`\n\nAny 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.\n\nTo get the latest LTS version of node and migrate your existing installed packages, use\n\n```sh\nnvm install 'lts/*' --reinstall-packages-from=current\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 node --reinstall-packages-from=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 6 --reinstall-packages-from=5\nnvm install v4.2 --reinstall-packages-from=iojs\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 lts/* --reinstall-packages-from=default --latest-npm\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 `, (2) delete the newly created node version (`nvm uninstall `), then (3) rerun your `nvm install` with the `--latest-npm` flag.\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/default-packages`. You can add anything npm would accept as a package argument on the command line.\n\n```sh\n# $NVM_DIR/default-packages\n\nrimraf\nobject-inspect@1.0.2\nstevemao/left-pad\n```\n\n### io.js\n\nIf you want to install [io.js](https://github.com/iojs/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 iojs --reinstall-packages-from=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/R = red / bold red\n\n g/G = green / bold green\n\n b/B = blue / bold blue\n\n c/C = cyan / bold cyan\n\n m/M = magenta / bold magenta\n\n y/Y = yellow / bold yellow\n\n k/K = black / bold black\n\n e/W = light grey / 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\nTo restore your PATH, you can deactivate it:\n\n```sh\nnvm deactivate\n```\n\nTo set a default Node version to be used in any new shell, use the alias 'default':\n\n```sh\nnvm alias default node\n```\n\nTo use a mirror of the node binaries, set `$NVM_NODEJS_ORG_MIRROR`:\n\n```sh\nexport NVM_NODEJS_ORG_MIRROR=https://nodejs.org/dist\nnvm install node\n\nNVM_NODEJS_ORG_MIRROR=https://nodejs.org/dist 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://iojs.org/dist\nnvm install iojs-v1.0.3\n\nNVM_IOJS_ORG_MIRROR=https://iojs.org/dist 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### .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/*\" > .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:\n\n```sh\n$ nvm use\nFound '/path/to/project/.nvmrc' with version <5.9>\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** be the `` (as described by `nvm --help`) followed by a newline. No trailing spaces are allowed, and the trailing newline is required.\n\n### Deeper Shell Integration\n\nYou 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).\n\nIf 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.\n\n#### bash\n\n##### Automatically call `nvm use`\n\nPut the following at the end of your `$HOME/.bashrc`:\n\n```bash\nfind-up() {\n path=$(pwd)\n while [[ \"$path\" != \"\" && ! -e \"$path/$1\" ]]; do\n path=${path%/*}\n done\n echo \"$path\"\n}\n\ncdnvm() {\n cd \"$@\";\n nvm_path=$(find-up .nvmrc | 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/A\" ]]; 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\n elif [[ -s $nvm_path/.nvmrc && -r $nvm_path/.nvmrc ]]; then\n declare nvm_version\n nvm_version=$(<\"$nvm_path\"/.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/A` if no local versions are found\n locally_resolved_nvm_version=$(nvm ls --no-colors \"$nvm_version\" | tail -1 | tr -d '\\->*' | 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/A\" ]]; 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}\nalias cd='cdnvm'\ncd $PWD\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\n##### Calling `nvm use` automatically in a directory with a `.nvmrc` file\n\nPut this into your `$HOME/.zshrc` to call `nvm use` automatically whenever you enter a directory that contains an\n`.nvmrc` file with a string t","has_starred","hub_user","immutable_tags_settings",{"_75":11,"_76":77},"enabled","rules",[78],".*","is_automated","permissions",{"_82":21,"_83":11,"_84":11},"read","write","admin","user","storage_size",320659599,"orgData","recentTags",[91],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":100,"_50":118,"_119":94,"_120":33,"_121":56,"_57":122,"_123":124,"_125":109,"_126":118,"_127":66,"_128":21},"content_type","creator",11094147,"full_size",320644508,"id",128915298,"images",[101],{"_102":103,"_104":105,"_106":107,"_108":109,"_110":111,"_112":113,"_114":107,"_115":-5,"_116":96,"_63":66,"_117":-5},"architecture","amd64","digest","sha256:5e671d35c1eb84c0231a1fe7a496f688b5df0120c5115e25326d911261d6cbe1","features","","last_pulled","2026-09-30T13:32:09.986504759Z","last_pushed","2020-12-06T14:24:26Z","os","linux","os_features","os_version","size","variant","2020-12-06T14:24:25.43168Z","last_updater","last_updater_username","media_type","latest","repository",10376876,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"selectedTag","attestationsUrl","routes/_layout.r.$namespace.$reponame.tags",{"_38":142,"_149":150,"_136":159,"_160":11},{"_40":143,"_42":144,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":145,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":146,"_79":11,"_80":148,"_85":33,"_86":87},[],[44],[56],{"_75":11,"_76":147},[78],{"_82":21,"_83":11,"_84":11},"tags",{"_151":64,"_152":-5,"_153":-5,"_154":155},"count","next","previous","results",[156],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":157,"_50":118,"_119":94,"_120":33,"_121":56,"_57":122,"_123":124,"_125":109,"_126":118,"_127":66,"_128":21},[158],{"_102":103,"_104":105,"_106":107,"_108":109,"_110":111,"_112":113,"_114":107,"_115":-5,"_116":96,"_63":66,"_117":-5},[],"canDeleteTags","actionData","errors"]

hzgood/docker-nvm-dev

Tags for hzgood/docker-nvm-dev