Installing fnm on macOS using recommended script & Brew sets incorrect path

[Mathias-S]

The fnm installation doesn't work on macOS when using the recommended script to install fnm (which uses Homebrew):

curl -fsSL https://fnm.vercel.app/install | bash

The script installs fnm to Homebrew's folder, typically /opt/homebrew/bin/fnm on macOS running ARM.

However, the installation script is hard coded to set $FNM_PATH to $HOME/Library/Application Support/fnm (which doesn't exist), so the code inserted into the shell file will have the incorrect path:

# fnm
FNM_PATH="/Users/myusername/Library/Application Support/fnm"
if [ -d "$FNM_PATH" ]; then
  export PATH="/Users/myusername/Library/Application Support/fnm:$PATH"
  eval "`fnm env`"
fi

This renders the installation broken unless the user manually corrects the path.

The README also incorrectly states that fnm is installed in that folder.

Workaround

Brew actually installs fnm correctly. If running fnm env in your terminal works, then you can update ~/.zshrc (or the corresponding shell file if you're using a different shell) and replace the aforementioned code with just the following:

eval "`fnm env`"

FNM_PATH isn't actually used by fnm, so it doesn't need to be set. Updating the PATH variable is also unnecessary if you've already verified that you can run fnm from your terminal.

[transfer1992]

I have exactly this experience on macOS right now.

[joseph-navant]

I just manually added /opt/homebrew/bin/fnm env --use-on-cd | source to my fnm.fish file

[Tedfulk]

@joseph-navant This worked! Thank You!

[joseph-navant]

@joseph-navant This worked! Thank You!

I finally moved this to the end of my config.fish because the previous workaround was giving me some issues when opening new tabs/windows:

# command hooks
fnm env --use-on-cd | source

[babhishek21]

I fixed this by setting the FNM_PATH to /Users/<my username>/.local/share/fnm in the shell script that the install script installs. You can verify this would work, by first running fnm env (which is what is being evaled / sourced) and checking the value of FNM_DIR in the output.

For my setup (fish shell), the sourcing happens in the /Users/<my username>/.config/fish/conf.d/fnm file:

# fnm
set FNM_PATH "/Users/<my username>/.local/share/fnm"
if [ -d "$FNM_PATH" ]
  set PATH "$FNM_PATH" $PATH
  fnm env | source
end

[SeasideLee]

I fixed this by setting the FNM_PATH to /Users/<my username>/.local/share/fnm in the shell script that the install script installs. You can verify this would work, by first running fnm env (which is what is being evaled / sourced) and checking the value of FNM_DIR in the output.

For my setup (fish shell), the sourcing happens in the /Users/<my username>/.config/fish/conf.d/fnm file:

# fnm
set FNM_PATH "/Users/<my username>/.local/share/fnm"
if [ -d "$FNM_PATH" ]
  set PATH "$FNM_PATH" $PATH
  fnm env | source
end

I do exactly the same as you do. How could such a stupid bug exist in such a widely used tool?

[jizhi0v0]

Works for me.Unbelievable