You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
The fnm installation doesn't work on macOS when using the recommended script to install fnm (which uses Homebrew):
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: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:FNM_PATH
isn't actually used by fnm, so it doesn't need to be set. Updating thePATH
variable is also unnecessary if you've already verified that you can runfnm
from your terminal.The text was updated successfully, but these errors were encountered: