π Fast and simple Node.js version manager, built in Rust
π Cross-platform support (Mac, Windows, Linux)
β¨ Single file, easy installation, instant startup
π Built with speed in mind
π€ Works with .node-version
and .nvmrc
files
For bash
, zsh
and fish
shells, there's an automatic installation script:
curl -fsSL https://fnm.vercel.app/install | bash
On OSX, it is a simple as brew upgrade fnm
.
On other operating systems, upgrading fnm
is almost the same as installing it. To prevent duplication in your shell config file add --skip-shell
to install command.
--install-dir
Set a custom directory for fnm to be installed. The default is $HOME/.fnm
.
--skip-shell
Skip appending shell specific loader to shell config file, based on the current user shell, defined in $SHELL
. e.g. for Bash, $HOME/.bashrc
. $HOME/.zshrc
for Zsh. For Fish - $HOME/.config/fish/conf.d/fnm.fish
--force-install
MacOS installations using the installation script are deprecated in favor of the Homebrew formula, but this forces the script to install using it anyway.
Example:
curl -fsSL https://fnm.vercel.app/install | bash -s -- --install-dir "./.fnm" --skip-shell
brew install fnm
Then, set up your shell for fnm
scoop install fnm
Then, set up your shell for fnm
cargo install fnm
Then, set up your shell for fnm
- Download the latest release binary for your system
- Make it available globally on
PATH
environment variable - Configure your shell profile:
fnm ships its completions with the binary:
fnm completions --shell <SHELL>
Where <SHELL>
can be one of the supported shells:
bash
zsh
fish
powershell
Please follow your shell instructions to install them.
fnm needs to run some shell commands before you can start using it.
This is done by evaluating the output of fnm env
. Check out the following guides for the shell you use:
add the following to your .bashrc
profile:
eval "$(fnm env)"
add the following to your .zshrc
profile:
eval "$(fnm env)"
create ~/.config/fish/conf.d/fnm.fish
add this line to it:
fnm env | source
add the following to the end of your profile file::
fnm env --use-on-cd | Out-String | Invoke-Expression
- On Windows, the profile is located at
~\Documents\PowerShell\Microsoft.PowerShell_profile.ps1
- For Mac/Linux, the profile is located at
~/.config/powershell/Microsoft.PowerShell_profile.ps1
fnm is also supported but is not entirely covered. You can set up a startup script and append the following line:
FOR /f "tokens=*" %i IN ('fnm env --use-on-cd') DO CALL %i
fnm [--shell=fish|bash|zsh] [--node-dist-mirror=URI] [--fnm-dir=DIR] [--log-level=quiet|error|info] <command>
- Providing
--shell=fish
will output the Fish-compliant version. Omitting it andfnm
will try to infer the current shell based on the process tree - Providing
--node-dist-mirror="https://npm.taobao.org/dist"
will use the Chinese mirror of Node.js - Providing
--fnm-dir="/tmp/fnm"
will install and use versions in/tmp/fnm
directory
You can always use fnm --help
to read the docs:
Installs [VERSION]
. If no version provided, it will install the version specified in the .node-version
or .nvmrc
files located in the current working directory.
Installs the latest LTS version of Node
Activates [VERSION]
as the current Node version. If no version provided, it will activate the version specified in the .node-version
or .nvmrc
file located in the current working directory.
--install-if-missing
β installs the version if it isn't installed yet
Display currently activated Node version.
Lists the installed Node versions.
Lists the Node versions available to download remotely.
Uninstalls the node version specified in [VERSION]
.
Aliases a Node version to a given name.
Aliases a Node version as default. Uses fnm alias
underneath.
Prints the required shell commands in order to configure your shell, Bash compliant if can't infer the shell. This command is highly influenced by the global options
--use-on-cd
will also output a script that will automatically change the node version if a.node-version
/.nvmrc
file is found
PRs welcome π
# Install Rust
git clone https://github.com/Schniz/fnm.git
cd fnm/
cargo build
cargo run -- --help # Will behave like `fnm --help`
cargo test