Unless you're doing a lot more serverside js than just running the build script for your react app you are not going to benefit much. Stick to whatever the active LTS version is and call it a day. Looking at the current schedule 18 goes into maintenance mode in late October. Answer from Santa_Fae on reddit.com
🌐
Auth0
auth0.com › docs › troubleshoot › product-lifecycle › deprecations-and-migrations › migrate-nodejs-22
Migrate from Node 18 to Node 22
Upgrade Actions to Node 22 by creating and deploying a new version of the existing implementation with any required changes and set to use Node 22 as the runtime. The runtime used for the remaining (non-Actions) extensibility offerings is defined ...
🌐
Medium
medium.com › @backendbyeli › migrating-from-node-js-18-20-to-22-7683067f603c
Node.js 22 Migration Guide: Upgrade from 18/20 Safely | Medium
2 weeks ago - Complete guide to migrating from Node.js 18/20 to 22 in production. Learn what breaks, performance improvements, testing strategies, and step-by-step upgrade process for backend applications.
🌐
Microsoft Learn
learn.microsoft.com › en-us › answers › questions › 2262448 › how-to-update-my-app-service-(node-version-18-to-2
How to update my app service (node version 18 to 22 ) ? - Microsoft Q&A
Run the following command in the Azure Cloud Shell to set your app to use Node.js version 22, az webapp config appsettings set --name <app-name> --resource-group <resource-group-name> --settings WEBSITE_NODE_DEFAULT_VERSION="22"
🌐
Upgradejs
upgradejs.com › blog › why-and-how-to-upgrade-to-nodejs-from-v18-to-v20m-v18.html
Why and How to Upgrade to Node.js From V18.x to V20.x - UpgradeJS.com | Node.js Upgrade Service
May 30, 2023 - The upgrade of the Node.js version is different for every application, the process can’t look like a one-size-fits-all solution. However, there are some general steps that you can follow to make the upgrade process as smooth as possible. In our The Basics Of The Node.js Version Upgrade Process opens a new window blog post we have explained the general steps that you can follow to upgrade your Node.js version.
🌐
Netlify
answers.netlify.com › features › updates
Builds + Functions + Plugins: Default Node.js version upgrade to 22 - Updates - Netlify Support Forums
January 3, 2025 - The default system Node.js version will be updated from version v18 → v22 on January 27, 2025. IMPORTANT UPDATE - This release been delayed to February 24, 2025 Why are we doing this?
🌐
Medium
medium.com › @Games24x7Tech › node-js-v20-upgrade-guide-best-practices-and-performance-insights-f76d7ace09ff
Node.js v20 upgrade guide: Best Practices and Performance Insights | by Games24x7 Blogs | Medium
September 6, 2024 - Node.js v20 upgrade guide: Best Practices and Performance Insights As of April 2023, Node.js versions less than v16 have reached their end of life, marking an essential milestone for developers and …
🌐
Node.js
nodejs.org › en › blog › announcements › v22-release-announce
Node.js — Node.js 22 is now available!
Testing your applications and modules with Node.js 22 helps to ensure the future compatibility of your project with the latest Node.js changes and features. Also of note is that Node.js 18 will go End-of-Life in April 2025, so we advise you ...
Find elsewhere
🌐
DEV Community
dev.to › jeromechoo › a-step-by-step-guide-to-updating-your-legacy-nodejs-app-in-2024-v10-to-v22-5h4h
A Step By Step Guide to Updating Your Legacy Node.js App in 2024 (v10 to v22) - DEV Community
July 18, 2025 - /home/node/app/node_modules/mongoose/lib/model.js:545 throw new MongooseError('Model.prototype.save() no longer accepts a callback'); ^ MongooseError: Model.prototype.save() no longer accepts a callback · Alas, callbacks out. Async in. But it was way too much work to refactor the code to use async functions, so I migrated all callbacks to use promises instead.
🌐
Medium
medium.com › @weijunext › node-22-1c02439bb767
Node 22: Major Improvements and How to Get Started | by Jude Wei | Medium
May 19, 2024 - By allowing require() to import ESM, developers can migrate modules one at a time instead of modifying the entire project at once. Currently, this approach is still experimental, so its use has some prerequisites: Start the command with the — experimental-require-module parameter, e.g. node — experimental-require-module app.js
🌐
Auth0
community.auth0.com › t › migrating-auth0-node-js-v18-to-v22 › 183227
Migrating Auth0 Node.js V18 to V22
The Auth0 Support Center is your resource for product help. Explore articles, join community discussions, and submit support tickets to get the answers you need.
🌐
Node.js
nodejs.org › en › blog › announcements › node-18-eol-support
Node.js — Beware of End-of-Life Node.js Versions - Upgrade or Seek Post-EOL Support
For Development Teams: Start by auditing your current Node.js usage. Check node --version across all your projects and environments. Create a migration timeline that targets 22 directly, skipping the 20 stepping stone.
🌐
DRC Systems
drcsystems.com › blogs › updates and new features in node.js 22 you don’t want to miss
What's New in Node.js 22: Features & Updates You Can’t Miss
September 25, 2025 - Upgrading to Node.js 22 is an exciting step that can bring numerous benefits to your projects. However, it’s important to approach the upgrade process methodically to ensure a smooth transition. Here’s a comprehensive guide to help you upgrade to Node.js 22 effectively:
Address   24th Floor, GIFT Two Building, Block No. 56, Road – 5C, Zone – 5, GIFT CITY, Gandhinagar, Taluka and District – Gandhinagar – 382 050 Gujarat, India, 382050
🌐
JavaScript in Plain English
javascript.plainenglish.io › node-js-24-vs-22-in-2025-whats-new-what-breaks-and-how-to-upgrade-safely-10725e1b7247
Node.js 24 vs 22 (2025): What’s New, What Breaks, How to Upgrade | JavaScript in Plain English
July 29, 2025 - Node 18 is EOL. Compare Node.js 22 LTS and 24: features, stability, performance, permission model, and safe upgrade steps. Decide the right version for 2025.
🌐
Businesscompassllc
businesscompassllc.com › home
Seamlessly Upgrading AWS Lambda Functions to Node.js 18 or 20: A Step-by-Step Guide - Business Compass LLC®
August 30, 2024 - Upgrading your AWS Lambda functions from Node.js 16 to Node.js 18 or 20 is essential to ensure the security, performance, and longevity of your cloud-based applications. By following the steps outlined in this guide and proactively addressing potential challenges, you can smoothly transition to the latest runtime versions. ... Node.js 20. x runtime is now available in AWS Lambda · wp_admin_interfinet2024-08-30T05:39:22-04:00August 30th, 2024|AWS, AWS Lambda, Node|Comments Off on Seamlessly Upgrading AWS Lambda Functions to Node.js 18 or 20: A Step-by-Step Guide
🌐
Objects
objects.ws › blog › node-js-22-lts-release
Node.js 22 LTS: Key Features & Migration Guide for Devs
August 26, 2025 - Click on any feature node above to explore its capabilities and benefits for your Node.js applications. ... An upgrade is not only the installation of the new binary. A planned migration will make the process compatible and downtime minimal. ... Make sure that vital libraries (Express, Prisma, NestJS, and many others) are compatible with Node.js 22.
Top answer
1 of 16
1868

Ubuntu Linux/Mac

The module n makes version-management easy:

sudo npm install n -g

For the latest stable version:

n stable

For the latest version:

n latest

Debian 10

Upgrade older versions of node and npm on Debian 10 as follows:

sudo su -c 'curl -sL https://deb.nodesource.com/setup_18.x | bash -'
sudo apt-get install nodejs -y
sudo apt update
sudo apt upgrade
sudo npm install -g [email protected]
node --version
npm --version

Note: Replace setup_18 with the latest long-term support release.

Windows

Just reinstall node from the .msi in Windows from the node website.

2 of 16
839

All Platforms (Mac, Linux & Windows) 2024

If you just need to upgrade your old version of Node.js to the latest one and don't need multiple versions, simply over-write your existing executable with the new one.

Download the Latest Node.js from nodejs.org/en/download

This Just Works! TM on all platforms and is the easiest/fastest method.
When you run node -v in your terminal you will see the the latest version.

Mac

If you originally installed Node.js using brew then run:

brew upgrade node

Managing Multiple Versions of Node.js:

If you need to run multiple versions of Node.js on your machine e.g. if you have an older project that targets a specific version on AWS Lambda, then NVM (Node Version Manger) is your friend!

Step 1 - Get NVM

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.3/install.sh | bash

If you're curious about the installation command read the source code
... its been reviewed by several node.js security experts

Step 2 - Install the Specific Version of Node.js you need

Once you've got NVM you can install a specific version of Node.js using the nvm command:

nvm install v22.16.0

Note: you may need to close & re-open your terminal window for nvm command to be available.

You should expect to see something like this in your terminal:

Now using node v22.16.0

You now have the latest Node.js on your machine.
And if you need to temporarily switch to a different/previous version, you can do it with a simple nvm command.

Note: avoid using sudo with Node/NPM as it violates the security principal of least privilege

NVM is considered "better" than N for managing multiple Node.js versions because the verbose commands mean it is much easier to keep track of what you are doing in your Terminal/SSH Log. It is used by the team at NPM the creators/custodians of the Node.js World!

🌐
Reddit
reddit.com › r/react › upgrading nodejs16 to nodejs18
r/react on Reddit: Upgrading nodejs16 to nodejs18
April 3, 2023 -

What are the checklists to use when upgrading from nodejs16 to nodejs18? The project also has some typescripts.

Top answer
1 of 1
1
Hey! I don't know if you already found an answer to your question, but I recently went through a similar update, although I started with version 11, so I went from 11 -> 16, then from 16 -> 18. One that I learned that you - strangely - do not have to pay much attention to is the Typescript version. I would recommend perceiving the Typescript and Nodejs upgrades as two different projects. I would recommend starting with nodejs, because it may have some deprecations of its own that you need to comply with for things to make sense. After that is merged and things are running, you should be able to just update to the most recent version of Typescript and fix the compilation errors, and you're back to speed with a brand new project! Here's a few of the things I went through to ensure things kept working as desired: In package.json ensure that engines.node is set to the new version For each of the packages you use, ensure that there is compatability between versions in one of two formats: Between the current version of the package AND the targeted node version Between (one of) the most recent version of the package AND the targeted node version If you're using some sort of CI, specify the image as node:18.11.0 if applicable If you desire: Update additional packages to most recent version. When updated to the most recent version of node its pretty safe to assume that all your libraries can support an update as well, as most are built against the most recent version of node at the time of creation. As I went through most of our core libraries, I ended up only having to update sharp, as it is a bit more intimately tied to nodejs. As you can tell, the checklist is surprisingly short, but feel free to let me know if you have additional questions, happy to help.