run `nvm use` automatically every time there's a .nvmrc file on the directory

Question

How to configure my shell so that nvm use run automatically every time there's a .nvmrc file on the directory and use the latest version or a global config when there's no .nvmrc file?

This use case is now documented in the **official nvm documentation** under [**Deep Shell Integration**](https://github.com/creationix/nvm#deeper-shell-integration). You can also see [my answer](https://stackoverflow.com/a/51349399/3966682) for the `bash` shell. — d4nyll, Feb 04 '19 at 12:01

score 219 · Answer 1 · edited Jun 08 '19 at 14:50

219

If you use zsh (z shell):

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

More info: https://github.com/creationix/nvm#zsh

edited Jun 08 '19 at 14:50

nck

41
3
7

answered Sep 15 '16 at 20:04

Rotareti

49,483
23
112
108

33

This worked really well for me, but caused a performance hit to `cd`, since it runs every time you change directories. I added `[[ -a .nvmrc ]] || return` to the first line of load-nvmrc(), and that significantly improved the performance of it – Belgabad Dec 05 '19 at 21:49
10

@Belgabad It's more performant, because with your line the script won't check for `.nvmrc` in parent directories and it also won't go back to the default `node` version when you `cd` out of the project dir. – Rotareti Dec 11 '19 at 21:38
@Belgabad where are you adding that line? before the `local` lines? – jtabone16 Mar 17 '21 at 02:43
3

If you're using `Powerlevel10k` don't forget to add `--silent` after `nvm use` to avoid console output warnings during zsh initialization – Liyali Sep 08 '21 at 10:22
1

it'd have been nice to have it check the version again when I checkout different branches in git on the same directory – khaled4vokalz Jun 22 '22 at 04:34
Anyone else get the follow output every time nvm use is executed? `sed: 8: " s#/Users/j ...": unterminated regular expression` – Jose Browne Nov 19 '22 at 17:38

score 94 · Answer 2 · edited Jun 23 '22 at 06:15

94

If you use bash you can add this to your ~/.bashrc file:

_nvmrc_hook() {
  if [[ $PWD == $PREV_PWD ]]; then
    return
  fi
  
  PREV_PWD=$PWD
  [[ -f ".nvmrc" ]] && nvm use
}

if ! [[ "${PROMPT_COMMAND:-}" =~ _nvmrc_hook ]]; then
  PROMPT_COMMAND="_nvmrc_hook${PROMPT_COMMAND:+;$PROMPT_COMMAND}"
fi

edited Jun 23 '22 at 06:15

jakubste

402
3
9

answered Jan 18 '18 at 13:16

devius

2,736
22
26

This is my preferred method. Thanks a ton for posting this! – Doug Barbieri Aug 04 '21 at 21:07
1

This broke direnv for me. – JohnOpincar Mar 04 '22 at 15:50
1

@JohnOpincar I think because it blew away the old `$PROMPT_COMMAND`. Try this for the last line instead: `export PROMPT_COMMAND="$PROMPT_COMMAND; enter_directory"` – Weston Ruter May 19 '22 at 23:28
I suggested an edit based on direnv code that doesn't overwrite previous `PROMPT_COMMAND` – jakubste Jun 22 '22 at 14:22

score 70 · Answer 3 · edited Jul 25 '22 at 18:59

70

Excellent answer from @devius.

I just extended it so it can revert to the default version when leaving a directory with .nvmrc to another without it.

~/.bashrc:

#
# Run 'nvm use' automatically every time there's 
# a .nvmrc file in the directory. Also, revert to default 
# version when entering a directory without .nvmrc
#
enter_directory() {
if [[ $PWD == $PREV_PWD ]]; then
    return
fi

PREV_PWD=$PWD
if [[ -f ".nvmrc" ]]; then
    nvm use
    NVM_DIRTY=true
elif [[ $NVM_DIRTY = true ]]; then
    nvm use default
    NVM_DIRTY=false
fi
}

export PROMPT_COMMAND="$PROMPT_COMMAND; enter_directory"

Following @doug-barbieri's suggestion, the script below will not change node back to the default version if there's no .nvmrc file in the current directory but there is one in the parent sub-directory.

~/.bashrc:

enter_directory() {
  if [[ $PWD == $PREV_PWD ]]; then
    return
  fi

  if [[ "$PWD" =~ "$PREV_PWD" && ! -f ".nvmrc" ]]; then
    return
  fi

  PREV_PWD=$PWD
  if [[ -f ".nvmrc" ]]; then
    nvm use
    NVM_DIRTY=true
  elif [[ $NVM_DIRTY = true ]]; then
    nvm use default
    NVM_DIRTY=false
  fi
}

The trick is here:

if [[ "$PWD" =~ "$PREV_PWD" && ! -f ".nvmrc" ]]; then
  return
fi

It checks if the PWD contains PREV_PWD. For example, if /home/user1/a/b contains /home/user1/a.

This can be extended to work with Starship (even on Git Bash for Windows not WSL) as well using the starship_precmd_user_func

set_win_title() {
  BASEPWD=$(basename "$PWD")
  echo -ne "\033]0;  $BASEPWD \a" < /dev/null
  if [[ $PWD == $PREV_PWD ]]; then
    return
  fi

  if [[ "$PWD" =~ "$PREV_PWD" && ! -f ".nvmrc" ]]; then
    return
  fi

  PREV_PWD=$PWD
  if [[ -f ".nvmrc" ]]; then
    nvm use
    NVM_DIRTY=true
  elif [[ $NVM_DIRTY = true ]]; then
    nvm use default
    NVM_DIRTY=false
  fi
}
starship_precmd_user_func="set_win_title"
eval "$(starship init bash)"

edited Jul 25 '22 at 18:59

B T

57,525
34
189
207

answered May 16 '18 at 19:06

Adriano P

2,045
1
22
32

Using bash on windows this returns `node v.0.0 (64-bit) is not installed.` even though the .nvmrc file has `9.3`. – hofnarwillie Jun 25 '18 at 20:24
2

Fixed by using `VERSION=$(cat .nvmrc); nvm use $VERSION` – hofnarwillie Jun 25 '18 at 20:30
I should also say that's using nvm-for-windows which is an entirely different beast. But with the above script + modification it works a treat. +1 – hofnarwillie Jun 25 '18 at 20:31
1

This doesn't work for me because if I happen to change to a sub-directory of the current project, it reverts to the default. So the detection needs to be a little smarter, looking up the directory tree for the first instance of `.nvmrc`. – Doug Barbieri Aug 04 '21 at 21:23
Instead of `export PROMPT_COMMAND=enter_directory` I think it should be `export PROMPT_COMMAND="$PROMPT_COMMAND; enter_directory"` to prevent clobbering the variable if it is set. – Weston Ruter May 19 '22 at 23:30
Also, if you move `PREV_PWD=$PWD` to the end of the function, you can change the second condition to `elif [[ $NVM_DIRTY = true ]] || [[ -z $PREV_PWD ]]; then` and then it will invoke `nvm use` when first starting a new terminal session before doing `cd`. – Weston Ruter May 20 '22 at 00:15
I had problems with the semicolor in `export PROMPT_COMMAND="$PROMPT_COMMAND; enter_directory"` and used `export PROMPT_COMMAND="$PROMPT_COMMAND; enter_directory"` instead. It works for me – kiril Mar 24 '23 at 14:08

score 44 · Accepted Answer · edited May 16 '22 at 16:09

44

I just found out about Automatic Version Switching for Node.js https://github.com/wbyoung/avn, you can use that.

npm install -g avn avn-nvm avn-n
avn setup

You can also follow this thread https://github.com/creationix/nvm/issues/110

edited May 16 '22 at 16:09

Jirik

1,435
11
18

answered May 09 '14 at 04:13

Gabo Esquivel

3,494
2
23
18

65

This is depressing.. is there no limit to the tool stack depth? node → npm → nvm → avn, and back up. *sigh* I'll play ball, but my passion is waning with each hack. (and thanks for the link, of course, gabo.) – hraban Dec 08 '17 at 12:35
None of the comments at the mentioned thread worked with bash for me. Maybe they're all for MacOS. For something that works in Ubuntu check my answer below. – devius Jan 18 '18 at 13:16
2

Unfortunately, [avn is no longer maintained](https://github.com/wbyoung/avn/issues/109), and @hraban objection is valid - also, `nvm` doesn't depend on `npm/node` by design, so throwing in another tool that requires `node` seems unwise. IMO direnv, per [R. Haluk Öngör's answer](https://stackoverflow.com/a/62095070/9238801) is the best way. direnv is shell agnostic, with few dependencies (and more importantly, doesn't depend on the tools it's supposed to manage) and is much more general while still usable and safe. – Matthew Strasiotto Oct 18 '22 at 06:15

score 37 · Answer 5 · edited May 13 '19 at 14:37

This answer is taken from the official nvm documentation.

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 "$@";
    nvm_path=$(find-up .nvmrc | tr -d '[:space:]')

    # 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=$(<"$nvm_path"/.nvmrc)

        # Add the `v` suffix if it does not exists in the .nvmrc file
        if [[ $nvm_version != v* ]]; then
            nvm_version="v""$nvm_version"
        fi

        # If it is not already installed, install it
        if [[ $(nvm ls "$nvm_version" | tr -d '[:space:]') == "N/A" ]]; then
            nvm install "$nvm_version";
        fi

        if [[ $(nvm current) != "$nvm_version" ]]; then
            nvm use "$nvm_version";
        fi
    fi
}
alias cd='cdnvm'

This is an improvement over:

@Gabo Esquivel's answer - because you won't have to switch to another tool (avn)
@devius's and @Adriano P's answers - which do not deal with situations where you are within a project

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.

@BossmanT By 'appears a little slow', do you mean you would guess it's slow from looking at what it does, or you actually found it slow to run? — callum, Sep 24 '19 at 08:54
@callum only from observing it running in my bash environment, no time trials were ran for it however, its about a fraction of a second slower, not anything significant of course — BossmanT, Sep 25 '19 at 15:01
I couldn’t detect any lag. Running `cd` isn’t something you’re ever likely to do in large batches, so I don’t think it matters unless the lag is noticeable to a human. — callum, Sep 25 '19 at 15:12
Thank you @d4nyll, this is really useful, added to my dotfiles — zigotica, Nov 30 '21 at 13:01
Note that the code from the official nvm documentation has been further updated. The problem with it is it is not compatible with `autojump`. So I think it is preferable to use the `PROMPT_COMMAND` approach above for that aspect. Here's what I mean: https://weston.ruter.net/2022/05/19/auto-nvm-use/ — Weston Ruter, May 20 '22 at 01:24

score 13 · Answer 6 · answered Nov 13 '19 at 16:58

I tried many solutions for this and nothing worked the way I wanted, so I wrote my own:

ZSH function to auto-switch to correct Node version

As far as I know, this is the only one that meets all the following criteria:

guarantees you are always on the right version by searching up the directory tree to find the closest .nvmrc (just like nvm use);
can handle any valid .nvmrc format;
clearly warns you if no installed version satisfies the .nvmrc,
assumes you want default if there is no .nvmrc anywhere up the tree;
is completely silent and fast if you are already on the correct Node version.

Great solution! I'm using it as it's quite fast, and also avoids overhead of keep calling nvm use — Luan Naufal, Nov 21 '22 at 21:17

score 8 · Answer 7 · answered Dec 22 '21 at 07:20

When you swim with the fish shell, here is how to run nvm use whenever there is a .nvmrc in the directory:

# TODO: save this as `$HOME/.config/fish/conf.d/use_nvmrc.fish` 

# HOW IT WORKS
# `nvm use` whenever .nvmrc is present in $PWD when using fish shell
# when traveling deeper, use the parent .nvmrc unless otherwise set
# also go back to default nvm when leaving the nvmrc-specified zone

function set_nvm --on-event fish_prompt
    # runs whenever the fish_prompt event occurs
    # if the current directory hasn't changed, do nothing
    string match -q $PWD $PREV_PWD; and return 1

    # if the current directory is within the previous one where we found an nvmrc
    # and there is no subsequent .nvmrc here, do nothing, we are in the same repo
    string match -eq $PREV_PWD $PWD; and not test -e '.nvmrc'; and return 1

    # if we clear those checks, keep track of where we are
    set -g PREV_PWD $PWD

    if test -e '.nvmrc'

        # if we find .nvmrc, run nvm use
        nvm use

        # and remember that we used that node
        set NVM_DIRTY true

    else if not string match $NVM_DIRTY true

        # if we have set nvm and have stepped out of that repo
        # go back to default node, if not already on it
        not string match -eq (nvm current) (nvm alias default); and nvm use default

        # and clear the flag
        set NVM_DIRTY
    end
end

score 5 · Answer 8 · answered May 29 '20 at 21:49

Yet another solution using direnv. Direnv comes with OS X and many distros so no installation is needed.

Add these two lines to your .zshenv or .bash_profile depending on which shell you use:


export NVM_DIR="$HOME/.nvm" # You probably have this line already
export NODE_VERSIONS="${NVM_DIR}/versions/node"
export NODE_VERSION_PREFIX="v"

Add an .envrc file to the project root with the contents

set -e
use node

Finally cd to your directory. (Don't forget to source .zshenv)

direnv will ask you to allow load config. Type direnv allow and voila!

Note that direnv doesn't support fancy constructs like lts/* in .nvrmc. On the positive side, direnv supports a bunch of runtimes like node, php, go, pyhton, ruby etc. allowing us to use a single tool to solve path issues.

Thanks, but I don't think direnv is included by default on MacOS — Suan, May 19 '21 at 18:33
Definitely not. `direnv` doesn't come with MacOs as of 12.5.1 — demisx, Aug 22 '22 at 19:22

score 4 · Answer 9 · answered Apr 27 '21 at 14:26

Bash version (to put in $HOME/.bashrc), with these features:

not using a cd alias (it allows to change directories in other ways, for example starting your terminal directly in another directory)
finds .nvmrc in upper directories (using nvm_find_nvmrc)
doesn't call nvm use if not needed

call_nvm_use_if_needed() {
  NEW_NVMRC="$(nvm_find_nvmrc)"
  if [[ "$NEW_NVMRC" != "$CURRENT_NVMRC" ]]; then
    if [[ -z "$NEW_NVMRC" ]]; then
      nvm use default
    else
      nvm use
    fi
    CURRENT_NVMRC="$NEW_NVMRC"
  fi
}

PROMPT_COMMAND="call_nvm_use_if_needed; ${PROMPT_COMMAND}"

doesn't seem to respect new folders after a CD on osx big sur — Mild Fuzz, Jun 22 '21 at 17:12

score 4 · Answer 10 · answered Nov 07 '21 at 02:01

For those on Apple Silicon (M1) Macs, you may have noticed NVM tries and fails to compile Node versions <16 from source on nvm install. Here's an update to @Rotareti's and @Reynke's answer that uses Rosetta to install the x86_64 version for Node < 16 while installing the native ARM version for Node >= 16, as Node 16 is the earliest version to support Apple Silicon.

Once installed, you can nvm use from either native or rosetta terminals to use the right version, so only the nvm install portion of the original function changes.

Replace /opt/homebrew/opt/nvm/nvm.sh with the path to your nvm installation.

~/.zshrc

# 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
      # check if we're in a native (ARM) terminal
      if [[ $(uname -p) == "arm" ]]; then
        local nvmrc_remote_version=$(nvm version-remote "$(cat "${nvmrc_path}")")

        if printf '%s\n%s\n' v16.0.0 "${nvmrc_remote_version}" | sort -VC; then
          # arm and node >= v16; install native node
          nvm install
        else
          # arm and node < v16; install x64 node using rosetta
          arch -x86_64 zsh -c '. "/opt/homebrew/opt/nvm/nvm.sh"; nvm install'
          nvm use
        fi
      else
        # not arm
        nvm install
      fi
    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

score 4 · Answer 11 · answered Dec 30 '21 at 22:52

This version will preserve `cd` performance

autoload -U add-zsh-hook
use_nvmrc_version_automatically() { 
  if [[ -f .nvmrc ]]; then
    echo ".nvmrc FOUND now INSTALLING and USING $(cat .nvmrc)"
    nvm install $(cat .nvmrc) && nvm use $(cat .nvmrc)
  fi
}
add-zsh-hook chpwd use_nvmrc_version_automatically
use_nvmrc_version_automatically

score 4 · Answer 12 · answered Feb 24 '22 at 01:37

4

There is now offical docs on how to do this really well, see deeper-shell-integration at https://github.com/nvm-sh/nvm#deeper-shell-integration

answered Feb 24 '22 at 01:37

LiveSource

6,230
4
21
20

This answer needs to bubble up to the top. The official https://github.com/nvm-sh/nvm repo should be the source of truth, with best solutions constantly updated through pull requests. StackOverflow isn't great for something like this which is expected to change over time. – stwr667 Jul 27 '23 at 02:48

albertpeiro · Answer 13 · 2021-06-23T19:19:42.360

If you use zsh (z shell):

I load nvm in a different way that's faster, but it means nvm_find_nvmrc is not available so @Rotareti solution wasn't working for me.

I found any easy way to fix: simply call nvm use without params since it already handles the logic of looking for an .nvmrc file itself and uses the default version if not found.

# ~/.zshrc

# DEFAULT NVM CONFIG
#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

# Add the following lines before all other OH MY ZSH config
# FASTER WAY TO CONFIGURE NVM ON STARTUP - OTHERWISE IT'S REALLY SLOW
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion"
export PATH="$NVM_DIR/versions/node/v$(<$NVM_DIR/alias/default)/bin:$PATH"
alias nvm="unalias nvm; [ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"; nvm $@"

# USE NVM VERSION IF .NVMRC FOUND, OTHERWISE USE DEFAULT
nvm use &>/dev/null

Altogether, I find this to be a really fast solution, that saves me the pain of typing nvm use.

I'd like to avoid nvm use when there's no .nvmrc file available, but loading time is quite low on my computer as it stands and I rarely need a terminal without Node - so this works for me for now.

Update: Added instructions on where to place suggested script

@MildFuzz Do you mean when you open a new terminal from a different location? If that's what you mean you need to add the suggested script to your .zshrc file before all the rest of zsh config. — albertpeiro, Jun 23 '21 at 19:16

score 2 · Answer 14 · answered Jul 13 '21 at 02:45

For zsh users, you should try zsh-nvm:

Zsh plugin for installing, updating, and loading nvm

Suppose you are using antigen, you can turn on auto use like this:

export NVM_AUTO_USE=true
antigen bundle lukechilds/zsh-nvm

zsh-nvm also supports lazy load nvm, which dramatically reduced the startup time of zsh

% time (source "$NVM_DIR/nvm.sh")
( source "$NVM_DIR/nvm.sh"; )  0.58s user 0.37s system 109% cpu 0.874 total

% time (_zsh_nvm_lazy_load)
( _zsh_nvm_lazy_load; )  0.01s user 0.01s system 168% cpu 0.012 total

laur · Answer 15 · 2018-08-13T16:19:59.940

Extending on @Adriano P answer, I'd propose this version that is less general (only works if .nvmrc is set on a git repository root), but works in cases when we navigate to elsewhere in project than its root:

_enter_dir() {
    local git_root
    git_root=$(git rev-parse --show-toplevel 2>/dev/null)

    if [[ "$git_root" == "$PREV_PWD" ]]; then
        return
    elif [[ -n "$git_root" && -f "$git_root/.nvmrc" ]]; then
        nvm use
        NVM_DIRTY=1
    elif [[ "$NVM_DIRTY" == 1 ]]; then
        nvm use default
        NVM_DIRTY=0
    fi
    PREV_PWD="$git_root"
}

export PROMPT_COMMAND=_enter_dir
#export PROMPT_COMMAND="$PROMPT_COMMAND;_enter_dir"  # use this if PROMPT_COMMAND already defined

score 1 · Answer 16 · answered Aug 13 '18 at 16:24

1

I use this zsh configuration framework called Oh My Zsh. It's a very active repository with regular updates. Try it and I'm sure you will love it. Oh, and it has the automatic .nvmrc feature built-in so it's as simple as installing the package thru npm!

https://github.com/robbyrussell/oh-my-zsh

answered Aug 13 '18 at 16:24

Satya Sampathirao

147
9

1

I don't think this functionality is build in – Mild Fuzz Jun 22 '21 at 17:10
1

It actually has it these days: if `NVM_AUTOLOAD` is set to `1`, the plugin will automatically load a node version when if finds a `.nvmrc` file in the current working directory indicating which node version to load. See: https://github.com/ohmyzsh/ohmyzsh/tree/master/plugins/nvm – Tuukka Mustonen Dec 03 '21 at 20:08

score 1 · Answer 17 · answered Jan 26 '19 at 14:59

For someone still facing the above issue the README for nvm has this section which would be helpful https://github.com/creationix/nvm#deeper-shell-integration

Personally I prefer editing the .bashrc (https://github.com/creationix/nvm#automatically-call-nvm-use) over other solutions.

score 1 · Answer 18 · answered Jul 14 '22 at 18:22

I've actually used Rotareti's solution for a while, before wanting to use the lts version if there is no .nvmrc (which was actually what the author asked originally).

So I worked on it a little and all it required was a few replaced/added lines:

# Load right version of NVM
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-remote --lts)" ]; then
    if [[ "$(nvm ls)" != *"$(nvm version-remote --lts)"* ]]; then
      echo "New lts version available. Installing..."
      nvm install --lts
    fi
    echo "Reverting to node lts version"
    nvm use --lts
  fi
}
add-zsh-hook chpwd load-nvmrc
load-nvmrc

score 0 · Answer 19 · answered Sep 30 '21 at 11:56

For users of Windows, zsh and coreybutler's nvm-windows, this slightly modified script adapted from the answer above could come in handy at the end of your .zshrc:

autoload -U add-zsh-hook
load-nvmrc() {
  if [ -f ".nvmrc" ]; then
    local required_version=$(cat .nvmrc | cut -c2-)
    local current_version=$(node -v)
    echo "Required Node version: $required_version"
    local is_available_already=$(nvm ls | grep -c "$required_version")
    if [[ $required_version != $current_version && $is_available_already -lt 1 ]]; then
        echo "Required version $required_version not installed, installing..."
        nvm install $required_version
    fi
    nvm use $required_version
  fi
}
add-zsh-hook chpwd load-nvmrc
load-nvmrc

run `nvm use` automatically every time there's a .nvmrc file on the directory

19 Answers19

This version will preserve `cd` performance

Linked

run `nvm use` automatically every time there's a .nvmrc file on the directory

19 Answers19

This version will preserve cd performance

Linked

This version will preserve `cd` performance