My project only runs on an old version of Node. What do I do?

Also searched as: How to downgrade to a previous Node version · Upgrade Node version · Node version not supported by Angular · Node Version Manager install: nvm command not found

Updated 3 October 2026

Short answer

Get it working on the version it was built for first, using a version manager such as nvm, so you have a working starting point. Then upgrade it one long-term-support release at a time, testing at each step, until it's on a supported version. Don't run it in production on the old one: Node.js says production apps should only use Active or Maintenance LTS releases, and Node 20 and everything older have reached end of life.

What's the problem

The app only installs or starts on an old Node version, maybe Node 12, 14 or 16. Your computer and your hosting have moved on. You can't run it, can't deploy it, and every upgrade attempt breaks something.

Why it happens

  • Node changes, and old code depended on old behaviour. Removed features, changed defaults and newer language rules break older code and older packages.
  • Packages are tied to Node versions. Old packages with compiled parts often won't build on new Node, and new packages often won't run on old Node.
  • Old versions stop getting fixes. Long-term-support releases get critical fixes for about 30 months. After end of life there are no more security fixes, which is why hosts eventually stop supporting them.

How to fix it

  1. Find the version it was built for. Check .nvmrc, .node-version, the engines field in package.json, the Dockerfile (FROM node:…) and the build settings.
  2. Install a version manager (nvm on Mac and Linux, nvm-windows on Windows), install that old version, and get the app running on it. This is your baseline.
  3. Write the version into an .nvmrc file, so everyone, and every host, uses the same one.
  4. Upgrade one LTS release at a time, for example 16 to 18, 18 to 20, 20 to 22, 22 to 24. At each step, reinstall, run it, fix what breaks, and update the packages that complain.
  5. Stop on a supported LTS release and update .nvmrc and your hosting's Node setting to match.
  6. Test the flows that matter after the final step, not just that it starts.

When to call Preventionlabs

If the version manager gets it running and each upgrade step is a handful of fixes, you can do this. Call us when the project is many versions behind, the packages it needs no longer exist for newer Node, and every step breaks more than it fixes. The first thing a resurrection delivers is an app that builds and starts on maintained dependencies, deployed in your own hosting account.

Submit your project for a free assessment

Free assessment. $10,000 AUD flat to get it live, only if we take it on and you go ahead.

Sources

  1. Node.js: Node.js Releasesofficial docsProduction applications should only use Active LTS or Maintenance LTS releases.
  2. Node.js: Node.js Releasesofficial docsLTS release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months.
  3. Node.js: Node.js Releases: release tableofficial docsv 20 Iron Apr 17, 2023 Mar 24, 2026 EOL
  4. Netlify: Manage build dependencieshosting platform docsAdd a .node-version or .nvmrc file to the site’s base directory in your repository.

Related

npm install fails on my old project. How do I fix it? Usually Node is too new for the project, the lockfile and package.json disagree, or a package needs build tools or no longer exists. Check each, in this order. Everything in my project is years out of date. How do I update it? Get it running exactly as it is first. Then update in small steps (runtime, then framework, then the rest), testing between each, and replace what's abandoned. npm ERESOLVE: unable to resolve dependency tree. What does it mean? Two packages want different versions of a shared one, often React. --legacy-peer-deps forces the install but hides the conflict. Update the odd one out instead. My deploy keeps failing. What do I do? The build log names it. Usually a different Node version, a lockfile out of sync, a missing setting, or a warning the host treats as an error.
← All of It used to work