
In the world of Node.js development, it’s common to juggle multiple versions of Node across different projects. Using a single global Node installation can lead to version conflicts, dependency issues, or surprises in production. That’s where **NVM (Node Version Manager)** shines: it enables you to install, switch, and manage multiple Node.js versions side by side on the same machine.



![https___dev-to-uploads.s3.amazonaws.com_uploads_articles_tns0q1sn1n531uk9e8mt.webp](https://prod-files-secure.s3.us-west-2.amazonaws.com/655b33b3-36d2-8121-828f-0003e6db7868/5b95a022-33d5-40c3-869f-ff4584d211f9/https___dev-to-uploads.s3.amazonaws.com_uploads_articles_tns0q1sn1n531uk9e8mt.webp?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=ASIAZI2LB466Q3NNLJHL%2F20251002%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20251002T134309Z&X-Amz-Expires=3600&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEJX%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLXdlc3QtMiJGMEQCIGpV1K%2FRWsJ487lrwMHcyLxGL63C3ulUCOsaskvX1kRpAiBmwRa8i7RpR6QzAXjhuxwpqValht454Bo3yVULll1%2BMCr%2FAwgtEAAaDDYzNzQyMzE4MzgwNSIMgnsNWfIZSFkzybcvKtwDEt53xYmVM4cB0W0tS6Chs4cALsMI5dk20sSAWA%2BDiqxpeCv6V4psj4x9sky3Aal9%2FX0qqpPAEvpfGFwUiWq7aBT2IQNNkZdBsia3EiCBmqdhLvuSUIRPVVxc6Xv%2B28RHwmmjqYbovdebVAVG6lmPTfiqMpYfTDQDCxDhot8hMK20jo%2FLtIQBEHdlXtchfnPZg1%2FWlDSjaGTOAgAdAWchRG4tR0xYh3mLnGuW%2BLq%2FpbrrEyJrmTu%2BTDyXUxFeAd4DtErl%2B0pGBtoUdjO%2BqyDXrodQ48trl8hx4JFoIVWjOX5G5DrHdW%2FkYke9I4CQyl%2FUzBoZWIQFhRdX%2BB7Fj9zhMXzbGu92hrTAqSG8A2Qs%2FSbMZWqilJ5A1IKdvCMAxFevrQg4r2C59OW%2FsrAd5ULVez%2Bc7Xjg79ffKb%2BzbxnxiJngW96ARcSvEKhauETAfC%2BnLqy9aZb3FxEqvVEMAF%2Bwrga%2Boj4zh603M79y7lTrgI590Dgt1IeD2kh788kRjCW1WT6DR6d%2FNdv8emKYokbAOC1CnScN5g6uLIrxZqfneK3eTNlSfjuQLYpAlX1MAZjuM5uSGQHKb0Ae6H%2FtfFz2zhliQRTPk94YRLvXkDARl1YjACp56366FzMYRW4w3Nz5xgY6pgESsKhtnGYoxwRAmoQQsZ%2Bz%2B6oSPwhpSoYch7H4XMxtoRSS54YGTJLzvpBT4kefi%2B4BG9LT5FF0iTEbYNtxNiAUBtFQmvFDeqMHuZ%2F72CWNl6VzHo45n3NFqdpiza8IDpsA7zsMa6PO2BFU6Slv4M72tA%2Fs8MJfWy4eVfjNNJfCH4Bi6Wp7YMbASq%2FgjOIoSTrgPvBWlCHJyE7NxG9kJCp6zPr1lUS3&X-Amz-Signature=07e811039bb242efb16b2b3fbd74a557659581a644f0a590564479a0561038df&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)


In this guide, I’ll walk you through installing NVM on **Ubuntu 24.04**, show you how to use it effectively, and offer best practices to keep your setup stable. Let’s get started.


## **Why Use NVM?**

1. **Switch Node.js versions seamlessly**: Perfect for projects that require specific Node versions.
2. **Isolated environments**: Run multiple Node.js versions without interference between them.
3. **User-friendly workflow**: Install, remove, and manage Node.js versions with simple command-line operations.

## **Step 1: Update Your System**


It’s crucial to update your system first, to ensure dependencies and package sources are current:


```bash
sudo apt update
sudo apt upgrade -y
```


Also, consider rebooting if you haven’t done that in a while, especially if kernel or low-level packages were upgraded.


## **Step 2: Install Necessary Tools**


You’ll need tools to download files and compile modules when required:


```bash
sudo apt install -y curl build-essential libssl-dev
```

- `curl` → For fetching remote scripts.
- `build-essential` → For compiling C/C++ add-ons (npm modules that need binaries).
- `libssl-dev` → Some Node versions/modules need SSL libraries.

## **Step 3: Download & Install NVM**


Here we fetch the official installer and run it:


```bash
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/vX.Y.Z/install.sh | bash
```

- Replace `vX.Y.Z` with the **latest stable NVM version**.
- This script creates a `.nvm` directory in your home (~/.nvm), and updates your shell config (like `~/.bashrc` or `~/.zshrc`) to load NVM automatically.

## **Step 4: Activating NVM in Your Shell**


After installation, you need to enable it:


```bash
# Either in current session:
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"

# Then, add these lines into ~/.bashrc or ~/.zshrc so they are loaded on login.
```


To apply changes right away:


```bash
source ~/.bashrc    # or source ~/.zshrc
```


## **Step 5: Confirming Installation**


Check NVM is available:


```bash
nvm --version
```


If this returns something like `0.40.x` (or whatever current), you’re good.


## **Step 6: Using NVM to Handle Node.js Versions**


With NVM ready, you’ll want to do things like:


### **Install the latest stable version**


```bash
nvm install node
```


### **Install the current LTS version**


```bash
nvm install --lts
```


### **Install a specific version**


```bash
nvm install 18.17.0
```


### **Switch to a version for current session**


```bash
nvm use 18.17.0
```


### **Set a default version, so new shells use it automatically**


```bash
nvm alias default 18.17.0
```


### **List versions you have installed**


```bash
nvm ls
```


### **See all Node.js versions available to install remotely**


```bash
nvm ls-remote
```


## **Step 7: Workflow Tips & Tricks**


These are the little practices that make your life easier:

- **Use a** **`.nvmrc`** **file:** In a project folder, put a file named `.nvmrc` with a version (e.g. `18.17.0`). Then you and your team can use `nvm use` inside that project to automatically pick the right version.
- **Global packages per version:** If you install global npm packages under one Node version, they won’t automatically be available under another. Use `-reinstall-packages-from=<old_version>` when installing a new version to copy over global packages.
- **Avoid mixing apt-installed Node with NVM:** If you had Node.js from Ubuntu’s package manager before, consider removing it (`sudo apt remove nodejs`) to avoid conflicts.

## **Step 8: Common Issues & Fixes**


Here are issues you might encounter, plus how to fix them:


| Problem                                        | Symptoms                                                      | Fix                                                                                                               |
| ---------------------------------------------- | ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| `nvm: command not found` after install         | The shell doesn’t load NVM automatically                      | Ensure lines added to `.bash` / `.zshrc` by installer are present; then `source` the file or open a new terminal. |
| Old Node still used by system                  | `node -v` returns old version even after `nvm use`            | Remove or disable the system Node; ensure your `PATH` is set so NVM’s bin comes first.                            |
| Permission errors when installing npm packages | Errors related to permissions when installing global packages | Don’t use `sudo` with npm when using NVM; global installs happen in user’s home directory.                        |


## **Conclusion**


Setting up NVM on Ubuntu 24.04 gives you control, flexibility, and peace of mind when working with Node.js. Once it’s in place, switching versions becomes second nature, which is especially helpful when maintaining multiple projects, testing compatibility, or just staying up to date with Node.js.



Managing Multiple Node.js Versions with NVM on Ubuntu 24.04: A Developer’s Guide


If you’ve ever found yourself copy-pasting data between tools, writing yet another one-off script to connect APIs, or juggling a dozen SaaS dashboards every day, you know the pain of repetitive work. That’s exactly where **n8n** comes in a tool I’ve been exploring recently, and honestly, it has quickly become one of my favorites for automation.


## So, What Exactly is n8n?


n8n (short for “node”) is an **open-source workflow automation platform**. Think of it as a more developer-friendly version of Zapier or Integromat. It lets you connect different services, APIs, and databases, and build workflows that run automatically, without needing to reinvent the wheel each time.


The best part? You can host it yourself, customize it however you want, and you’re not locked into someone else’s SaaS pricing model. For developers and teams who care about data ownership and flexibility, this is a huge plus.


## Why I Like Working with n8n


When I started tinkering with n8n, a few things immediately stood out:

- **It’s open-source and self-hostable.** You can run it locally, on a server, or even in Docker/Kubernetes. This gives you full control.
- **It comes with 350+ integrations.** Google Sheets, Slack, GitHub, AWS, databases - you name it.
- **The editor is visual, but not limiting.** You can drag-and-drop nodes, but you can also write custom JavaScript if you need more control.
- **Event-driven automation.** Workflows don’t just run on a schedule - they can trigger when something happens (like a new file uploaded, or a webhook received).

For me, it strikes the right balance between **low-code convenience** and **developer power**.


## Real-Life Use Cases


Here are a few scenarios where n8n shines:

- **Marketing automation**: A new lead fills out a form → n8n saves it to a CRM → sends a Slack notification → triggers a welcome email.
- **DevOps monitoring**: When a server goes down → log the issue → create a GitHub ticket → ping the on-call engineer.
- **Data pipelines**: Fetch data from an API → transform it → insert it into PostgreSQL or BigQuery.
- **E-commerce workflows**: Automate order tracking, payments, and shipping updates.

Basically, if you can describe a process, you can probably build it in n8n.


## Getting Started (It’s Easier Than You Think)


Setting up n8n is surprisingly straightforward. You can install it globally with npm:


```bash
npm install n8n -g
n8n start
```


Or, if you’re like me and prefer containers:


```bash
docker run -it --rm \
  -p 5678:5678 \
  -v ~/.n8n:/home/node/.n8n \
  n8nio/n8n
```


Then just head over to `http://localhost:5678` in your browser, and you’ll find a clean visual editor waiting for you. From there, it’s drag-and-drop nodes, configure credentials, and connect the dots.


## Why n8n is Worth a Try


There are plenty of automation tools out there, but what sets n8n apart is the **balance of simplicity and flexibility**. It’s approachable for non-developers, but at the same time, it doesn’t box developers in. You can go as deep as you want with scripting, custom nodes, and API integrations.


For me, it’s a tool that reduces repetitive work and lets me focus on more interesting problems. If you’re curious about automation, I’d definitely recommend giving it a try.



Automating Workflows with n8n: Why I Use It and Why You Might Too


In the world of Node.js development, it’s common to juggle multiple versions of Node across different projects. Using a single global Node installation can lead to version conflicts, dependency issues, or surprises in production. That’s where **NVM (Node Version Manager)** shines: it enables you to install, switch, and manage multiple Node.js versions side by side on the same machine.



![https___dev-to-uploads.s3.amazonaws.com_uploads_articles_tns0q1sn1n531uk9e8mt.webp](https://prod-files-secure.s3.us-west-2.amazonaws.com/655b33b3-36d2-8121-828f-0003e6db7868/5b95a022-33d5-40c3-869f-ff4584d211f9/https___dev-to-uploads.s3.amazonaws.com_uploads_articles_tns0q1sn1n531uk9e8mt.webp?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=ASIAZI2LB466XNLKYYMD%2F20251002%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20251002T134309Z&X-Amz-Expires=3600&X-Amz-Security-Token=IQoJb3JpZ2luX2VjEJX%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLXdlc3QtMiJGMEQCIBjNh8x38bFkkBvLR0Vevnuf1RKOM%2BK00KDrefucq%2BGZAiAJ%2Fyjv4xc01f1lZXunemq6Qr3oDlV6SFQiCPPj7SAJryr%2FAwgtEAAaDDYzNzQyMzE4MzgwNSIMxE5ESbwX1UyYjLiEKtwDnPw9jJLyvFn7MCuIysKbQRCNg8cB6V%2Fa9riGt%2BsoPSqY0OwXKUkPr3fS4kGZXhQnyPVXeYiE6shv5OQvJ08cyHQ2p27O%2FA0lIealTXlGgUsqbd%2BJdokYtUTGFlGYa7D0i2Utg3tz6LDj7k24lbVGZjoP44dtouRteypBQjX3tppUDJc5IwYqeoXCEaZgyyaBGag%2BlCCNyVj6eJNIAxSpztBvsa4Y3IXZXIeas3lfS22BR6C6H9IoDgEuMSMpnf5bwiGhtNbQ6XomZcsuMSB4drWa7qNEPRpMiyIZocXjFaDqSyfpm9G%2B9bGNXRjUq0wj1mqte62QGYnUNSFSWWcg6gzle79uB%2BwePskpIbVzM6UZ%2FH7VR4d33uai5yzv7r5uzhFZ1YRLmHybnvGHfOlfGmTa4oIUJLqkRSkoFvhopLxzilgVd3Sfxj%2BGnf1Q1bQVy%2ByPoxfqnTsXbTv%2Fl5gCZEqO2K3%2BkKihazzDSwHU4NFz2R0gszpnu1VTPfv59%2BPCU%2BD7ek4izyCX0FlPS%2Bqtv0leb2VIjhrIF98Cvja0mKJ6w7g9dPMFLrF7AS%2Bp7GdxL2ACBPpJVGSBVjCGTuRKs833Z6QuzJYGFlehOXJP5IQqjQZ%2BfntaHK93FLMw3Nz5xgY6pgHlE70KQ7BlACi8wnUwzqL4oJzmbbZCXDw2ioTg3zl36FCEFqQxyF8WpqQ7hRxMwxe5JSt4h4wkYY%2Fx4FMs38lfnS%2FAzC%2B6EbpVUeMO%2FY%2BThPPxw906laxW9pBK8DHiwn2OspvlNC8MDdaHvqIVCnmgWnHyfGfdFy24jwarALKgKaFSF1HIH%2FhSnJ2EYOM9%2FwyedpPeEEguXdPDk0Twdz002K7u1SwS&X-Amz-Signature=566144d0f0a188702de3ef46bc4edf8dab422cb1d250e2cfa6b5b71d9fb7035b&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)


In this guide, I’ll walk you through installing NVM on **Ubuntu 24.04**, show you how to use it effectively, and offer best practices to keep your setup stable. Let’s get started.


## **Why Use NVM?**

1. **Switch Node.js versions seamlessly**: Perfect for projects that require specific Node versions.
2. **Isolated environments**: Run multiple Node.js versions without interference between them.
3. **User-friendly workflow**: Install, remove, and manage Node.js versions with simple command-line operations.

## **Step 1: Update Your System**


It’s crucial to update your system first, to ensure dependencies and package sources are current:


```bash
sudo apt update
sudo apt upgrade -y
```


Also, consider rebooting if you haven’t done that in a while, especially if kernel or low-level packages were upgraded.


## **Step 2: Install Necessary Tools**


You’ll need tools to download files and compile modules when required:


```bash
sudo apt install -y curl build-essential libssl-dev
```

- `curl` → For fetching remote scripts.
- `build-essential` → For compiling C/C++ add-ons (npm modules that need binaries).
- `libssl-dev` → Some Node versions/modules need SSL libraries.

## **Step 3: Download & Install NVM**


Here we fetch the official installer and run it:


```bash
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/vX.Y.Z/install.sh | bash
```

- Replace `vX.Y.Z` with the **latest stable NVM version**.
- This script creates a `.nvm` directory in your home (~/.nvm), and updates your shell config (like `~/.bashrc` or `~/.zshrc`) to load NVM automatically.

## **Step 4: Activating NVM in Your Shell**


After installation, you need to enable it:


```bash
# Either in current session:
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"

# Then, add these lines into ~/.bashrc or ~/.zshrc so they are loaded on login.
```


To apply changes right away:


```bash
source ~/.bashrc    # or source ~/.zshrc
```


## **Step 5: Confirming Installation**


Check NVM is available:


```bash
nvm --version
```


If this returns something like `0.40.x` (or whatever current), you’re good.


## **Step 6: Using NVM to Handle Node.js Versions**


With NVM ready, you’ll want to do things like:


### **Install the latest stable version**


```bash
nvm install node
```


### **Install the current LTS version**


```bash
nvm install --lts
```


### **Install a specific version**


```bash
nvm install 18.17.0
```


### **Switch to a version for current session**


```bash
nvm use 18.17.0
```


### **Set a default version, so new shells use it automatically**


```bash
nvm alias default 18.17.0
```


### **List versions you have installed**


```bash
nvm ls
```


### **See all Node.js versions available to install remotely**


```bash
nvm ls-remote
```


## **Step 7: Workflow Tips & Tricks**


These are the little practices that make your life easier:

- **Use a** **`.nvmrc`** **file:** In a project folder, put a file named `.nvmrc` with a version (e.g. `18.17.0`). Then you and your team can use `nvm use` inside that project to automatically pick the right version.
- **Global packages per version:** If you install global npm packages under one Node version, they won’t automatically be available under another. Use `-reinstall-packages-from=<old_version>` when installing a new version to copy over global packages.
- **Avoid mixing apt-installed Node with NVM:** If you had Node.js from Ubuntu’s package manager before, consider removing it (`sudo apt remove nodejs`) to avoid conflicts.

## **Step 8: Common Issues & Fixes**


Here are issues you might encounter, plus how to fix them:


| Problem                                        | Symptoms                                                      | Fix                                                                                                               |
| ---------------------------------------------- | ------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| `nvm: command not found` after install         | The shell doesn’t load NVM automatically                      | Ensure lines added to `.bash` / `.zshrc` by installer are present; then `source` the file or open a new terminal. |
| Old Node still used by system                  | `node -v` returns old version even after `nvm use`            | Remove or disable the system Node; ensure your `PATH` is set so NVM’s bin comes first.                            |
| Permission errors when installing npm packages | Errors related to permissions when installing global packages | Don’t use `sudo` with npm when using NVM; global installs happen in user’s home directory.                        |


## **Conclusion**


Setting up NVM on Ubuntu 24.04 gives you control, flexibility, and peace of mind when working with Node.js. Once it’s in place, switching versions becomes second nature, which is especially helpful when maintaining multiple projects, testing compatibility, or just staying up to date with Node.js.



Technical Blog

Managing Multiple Node.js Versions with NVM on Ubuntu 24.04: A Developer’s Guide

Automating Workflows with n8n: Why I Use It and Why You Might Too