How do I set up fnm to automatically switch Node versions when I cd into a project?

Add the --use-on-cd flag to your shell eval command, as shown in the README for each shell. This makes fnm detect .node-version or .nvmrc files and switch versions automatically upon directory changes.

fnm vs nvm: which is better for Node.js version management?

fnm is faster and built in Rust, offering better cross-platform support and performance out of the box. nvm is more established with a larger community, but fnm excels in speed and simplicity for modern workflows.

Can I use fnm with Docker containers?

Yes, install fnm via release binaries or cargo in Docker images, but since containers often use fixed Node versions, version management is less critical than in local development. Ensure shell integration is configured if needed.

How to install fnm on Windows without package managers like Winget?

Download the latest release binary from GitHub, add it to your PATH, and manually set up shell integration for PowerShell or Command Prompt using the eval commands provided in the README.

Does fnm manage npm versions separately from Node.js?

No, fnm focuses solely on Node.js version management. npm versions are tied to Node.js releases, so switching Node versions changes npm accordingly, but fnm doesn't offer independent npm version control.

What happens if I have both .node-version and .nvmrc files in a project?

fnm prioritizes .node-version files over .nvmrc, as implied by the README's documentation. Ensure only one is present to avoid conflicts, or rely on the default precedence.

Open-Awesome

fnm

GPL-3.0Rustv1.39.0

A fast and simple Node.js version manager built in Rust, supporting cross-platform development.

Visit Website GitHub

26.3k stars639 forks0 contributors

What is fnm?

fnm (Fast Node Manager) is a Node.js version manager built in Rust that allows developers to quickly install, switch, and manage multiple Node.js versions. It solves the problem of handling different Node.js versions across projects with a focus on speed and cross-platform compatibility.

Target Audience

Node.js developers working on multiple projects requiring different Node.js versions, especially those using macOS, Windows, or Linux who value performance and simplicity.

Value Proposition

Developers choose fnm for its blazing-fast performance due to being written in Rust, easy installation process, and seamless integration with existing version files like `.nvmrc` and `.node-version`.

Overview

🚀 Fast and simple Node.js version manager, built in Rust

Use Cases

Best For

Managing multiple Node.js versions across different projects
Fast switching between Node.js versions in development workflows
Cross-platform development teams using macOS, Windows, and Linux
Automating Node.js version selection with `.node-version` files
Shell integration with Bash, Zsh, Fish, or PowerShell
Performance-critical environments where version manager speed matters

Not Ideal For

Teams relying heavily on Windows Command Prompt without modern shell upgrades or workarounds
Developers needing integrated management of npm versions separately from Node.js
Environments with strict security policies that block automatic curl-based installation scripts

Pros & Cons

Pros

Blazing Fast Performance

Built with Rust, fnm ensures instant startup and rapid version switching, as emphasized in the README's focus on speed and the 'Blazing fast!' branding.

Cross-Platform Simplicity

Works consistently on macOS, Windows, and Linux with easy installation via package managers like Homebrew, Winget, or single-file scripts, reducing setup friction.

Easy Version File Integration

Automatically reads .node-version and .nvmrc files to switch Node.js versions when entering project directories, streamlining multi-project workflows.

Comprehensive Shell Support

Integrates seamlessly with Bash, Zsh, Fish, PowerShell, and even provides workarounds for Windows Command Prompt, covering most developer environments.

Cons

Manual Shell Configuration

Requires users to manually edit shell profiles (e.g., .bashrc, .zshrc) for setup, which can be error-prone and less intuitive for beginners or automated deployments.

Incomplete Windows CMD Support

The README explicitly states that support for Windows Command Prompt is 'not entirely covered,' necessitating additional scripts or reliance on modern shells like PowerShell.

Deprecated Installation Methods

On macOS, the script-based installation is deprecated in favor of Homebrew, which may confuse users and add complexity for those preferring curl-based setups.

Open Source Alternative To

fnm is an open-source alternative to the following products:

nvm

nvm (Node Version Manager) is a command-line tool that allows developers to install and switch between multiple versions of Node.js on a single machine.

n is a Node.js version manager that allows developers to install, switch between, and manage multiple Node.js versions via the command line.

Frequently Asked Questions

Related Projects

nvm for Windows

A node.js version management utility for Windows. Ironically written in Go.

Stars47,147

Forks3,857

Last commit3 months ago

Node version management

Stars19,514

Forks762