Schniz/fnm is a Rust project with 27.4k stars in the Frontend space. 🚀 Fast and simple Node.js version manager, built in Rust
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
🚀 Fast and simple Node.js version manager, built in Rust
Features
🌎 Cross-platform support (macOS, Windows, Linux)
✨ Single file, easy installation, instant startup
🚀 Built with speed in mind
📂 Works with .node-version and .nvmrc files
Installation
Using a script (macOS/Linux)
For bash, zsh and fish shells, there's an automatic installation script.
First ensure that curl and unzip are already installed on your operating system. Then execute:
curl -fsSL https://fnm.vercel.app/install | bash
Upgrade
On macOS, it is as 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, pass --skip-shell to the install command:
Set a custom directory for fnm to be installed. The default is $XDG_DATA_HOME/fnm (if $XDG_DATA_HOME is not defined it falls back to $HOME/.local/share/fnm on linux and $HOME/Library/Application Support/fnm on MacOS).
Note: On macOS, this option is only meaningful when using --force-install since Homebrew is the default installation method.
--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.
Download the latest release binary for your system
Make it available globally on PATH environment variable
Set up your shell for fnm
Removing
To remove fnm (😢), just delete the .fnm folder in your home directory. You should also edit your shell configuration to remove any references to fnm (ie. read Shell Setup, and do the opposite).
Completions
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.
Shell Setup
Environment variables need to be setup before you can start using fnm.
This is done by evaluating the output of fnm env.
[!TIP]
Prefer passing an explicit shell (for example fnm env --shell bash) instead of relying on shell inference at runtime. It is a bit faster and avoids process tree detection.
[!NOTE]
Check out the Configuration section to enable highly
recommended features, like automatic version switching.
Adding a .node-version to your project is as simple as:
To create the profile file you can run this in PowerShell:
if (-not (Test-Path $profile)) { New-Item $profile -Force }
To edit your profile run this in PowerShell:
Invoke-Item $profile
Windows Command Prompt aka Batch aka WinCMD
fnm is also supported but is not entirely covered. You can set up a startup script for cmd.exe or Windows Terminal and append the following lines:
@echo off
:: for /F will launch a new instance of cmd so we create a guard to prevent an infnite loop
if not defined FNM_AUTORUN_GUARD (
set "FNM_AUTORUN_GUARD=AutorunGuard"
FOR /f "tokens=*" %%z IN ('fnm env --use-on-cd') DO CALL %%z
)
Usage with Cmder
Usage is very similar to the normal WinCMD install, apart for a few tweaks to allow being called from the cmder startup script. The example assumes that the CMDER_ROOT environment variable is set to the root directory of your Cmder installation.
Then you can do something like this:
Make a .cmd file to invoke it
:: %CMDER_ROOT%\bin\fnm_init.cmd
@echo off
FOR /f "tokens=*" %%z IN ('fnm env --use-on-cd') DO CALL %%z
The most recent commit recorded on Schniz/fnm was 3 months ago, based on the GitHub push timestamp. The repository has 665 forks — one of the better signals of community interest.
How many stars does Schniz/fnm have?
Schniz/fnm has 27.4k GitHub stars — refresh the page for the live number, or check github.com/Schniz/fnm. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is Schniz/fnm open source?
Yes — Schniz/fnm ships under the GPL-3.0 license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/Schniz/fnm.
What else is in the Frontend space?
Schniz/fnm is tracked by TopGit under the Frontend category, alongside 6 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What is Schniz/fnm?
Schniz/fnm (Schniz/fnm) is a Rust project on GitHub. From the project's own README: 🚀 Fast and simple Node.js version manager, built in Rust
What language is Schniz/fnm written in?
Schniz/fnm is written primarily in Rust. GitHub's language field is based on the largest share of bytes in the default branch.
What license does Schniz/fnm use?
Schniz/fnm is released under the GPL-3.0 license. Always verify the LICENSE file directly on GitHub for the authoritative terms — license strings can be edited out of sync with a project's actual stance.
Where do I read more about Schniz/fnm?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/Schniz/fnm is the definitive source.
Read full README in the tab above.
Is fnm worth your time?
ChatGPT, Claude and Perplexity can all read this page. Ask one of them what it makes of fnm.