Mastering Node.js Version Management with Fast Node Manager (fnm)

Node.js Version Management Introduction Guide

When dealing with multiple projects that require different running environments, managing multiple Node.js versions may be tricky. The traditional installation program can only install a single Node.js version, and Fast Node Manager (FNM) provides a flexible and efficient solution that can seamlessly switch the Node.js version.

What is FNM?

FNM is a fast and simple Node.js manager written in Rust ⚡.

Why use FNM?

Before deeper installation and use, let us understand the advantage of FNM:

Fast version switching
1. : The Node.js version in real time, without the need for complex unloading process. The configuration of the project
: Set different Node.js versions for different projects.
2. Lightweight and fast : Unlike other versions of managers, the design goals of FNM are lightweight and high performance.
3. Cross -platform support : can run stably on Windows, Macos and Linux.
4. FNM installation steps 1. Installation method

Macos and Linux:

Windows:

<code class="language-bash"># 使用 curl
curl -fsSL https://fnm.vercel.app/install | bash

# 使用 shell 脚本的替代方法
wget -qO- https://fnm.vercel.app/install | bash</code>

2. PowerShell configuration

Add the following to the end of the PowerShell configuration file:

<code class="language-bash"># 使用 winget
winget install Schniz.fnm

# 使用 scoop
scoop install fnm</code>

<code class="language-bash">eval "$(fnm env --use-on-cd)"</code>

Note

<code class="language-powershell">fnm env --use-on-cd --shell powershell | Out-String | Invoke-Expression</code>

You need to find the Powershell configuration file. If there is no existence, create it. The following explains how to operate.

For macos/linux, the configuration file is located:

For Windows, the position is:

PowerShell 5

<code>~/.config/powershell/Microsoft.PowerShell_profile.ps1</code>

If the configuration file does not exist,

To create a configuration file

<code>%userprofile%\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 </code>

, you can run the following command in Powershell:

<code>%userprofile%\Documents\PowerShell\Microsoft.PowerShell_profile.ps1 </code>

To edit the configuration file in PowerShell, run the following command:

Run this command and add the first Powershell command to the end of the Powershell configuration file.

<code class="language-powershell">if (-not (Test-Path $profile)) { New-Item $profile -Force }</code>

This will enable automatic node.js version switching, you can easily use multiple Node.js versions.

FNM basic setting process

<code class="language-powershell">Invoke-Item $profile</code>

If you encounter any errors, for example, "I can't find the FNM environment variable", it may be related to the shell configuration you use!

Install Node.js version

Management of the installed version

<code class="language-bash"># 下载并安装 fnm：
winget install Schniz.fnm
# 下载并安装 Node.js：
fnm install 22
# 选择版本
fnm use 22  
# 验证 Node.js 版本：
node -v # 应该打印 "v22.13.1"。
# 验证 npm 版本：
npm -v # 应该打印 "10.9.2"。</code>

Current Node version

<code class="language-bash"># 安装最新的 LTS 版本
fnm install --lts
fnm i --lts

# 安装特定版本
fnm install 16.14.2

# 安装最新版本
fnm install latest</code>

<code class="language-bash"># 列出所有已安装的 Node.js 版本
fnm ls

# 列出所有远程 Node.js 版本
fnm ls-remote

# 设置默认全局 Node.js 版本
fnm default 22.13.1

# 在当前 shell 中使用特定版本
fnm use 22.13.1</code>

Edition alias

The version of the project is specific to the project

Create a

file in the project root directory to automatically use the specific node.js version:

<code class="language-bash">fnm current</code>

Now, when you enter the project directory, FNM will automatically switch to the specified version.

Best Practices

1. For production projects, always use LTS (Long Term Support) releases.
2. Update fnm regularly to get the latest features and improvements.
3. Use .node-version or .nvmrc files to maintain consistency across development teams.

Troubleshooting

If you have problems:

• Make sure fnm is properly added to your PATH
• Verify shell configuration
• Use fnm --version to check fnm version

Conclusion

Fast Node Manager simplifies Node.js version management, providing developers with a flexible and efficient tool to handle multiple runtime environments. By following these steps, you can easily switch between Node.js versions and maintain project-specific configurations.

If you enjoyed this post, please like or comment ❤ or share it with your community. You can also follow me on X ? or LinkedIn ?‍?

The above is the detailed content of Mastering Node.js Version Management with Fast Node Manager (fnm). For more information, please follow other related articles on the PHP Chinese website!