npm install fails on my old project. How do I fix it?

Also searched as: npm install error · How to fix npm install error · npm install error code ENOENT · npm ERR! code 1 · How do I do a clean install (delete node_modules and install) with npm?

Updated 3 October 2026

Short answer

Read the first error, not the last line. On an old project, npm install usually fails for one of four reasons: your Node version is much newer than the project expects, the lockfile and package.json disagree, a package has to compile native code and the build tools aren't installed, or a package has been removed or renamed. Install the Node version the project was built with, do a clean install, and work forward from there.

What's the problem

You clone the project or open it after a long gap, run npm install, and get a wall of red: "npm ERR! code 1", "gyp ERR!", "ENOENT", "unable to get local issuer certificate". Nothing has changed in the code. The world around it has.

Why it happens

  • Node moved on. The project was written for a Node version that's now years old. Node 20 and everything before it are end of life. Packages written for old Node often won't build on new Node, and vice versa.
  • The lockfile and package.json disagree. A clean install with npm ci stops with an error rather than guessing.
  • Native packages need compiling. Some packages (image processing, encryption, older Sass) compile code during install. That needs Python and C++ build tools, and old versions of those packages may not compile on new Node at all.
  • Packages disappear or move. Old versions get deprecated or removed, and some packages get renamed or abandoned.
  • Your network is in the way. "Unable to get local issuer certificate" usually means a corporate proxy or antivirus is intercepting secure connections.

How to fix it

  1. Find the Node version the project expects. Look for an .nvmrc or .node-version file, the engines field in package.json, a Dockerfile, or build settings. The age of the last commit is a rough guide too.
  2. Install that version with a version manager (nvm, or nvm-windows on Windows) and switch to it for this project.
  3. Do a clean install. Delete node_modules and run npm ci. If npm ci complains the lockfile doesn't match, run npm install once and commit the updated lockfile.
  4. For native build errors (gyp, Visual C++, Python), install your platform's build tools, or update that package to a version that ships prebuilt binaries.
  5. For certificate errors, configure npm to trust your network's certificate. Don't switch off certificate checking.
  6. Once it installs and runs on the old version, record the version in an .nvmrc file, then plan the upgrade to a supported Node release. See the project only runs on an old version of Node.

When to call Preventionlabs

If the right Node version and a clean install get it running, you're through the hardest part. Call us when it's still failing after that, because packages no longer exist, nothing compiles, or each fix exposes another. 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 Releases: release tableofficial docsv 20 Iron Apr 17, 2023 Mar 24, 2026 EOL
  3. npm: npm ciofficial docsIf dependencies in the package lock do not match those in package.json, npm ci will exit with an error, instead of updating the package lock.
  4. Netlify: Manage build dependencieshosting platform docsAdd a .node-version or .nvmrc file to the site’s base directory in your repository.

Related

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 project only runs on an old version of Node. What do I do? Run it on its old version with a version manager so it works again, then upgrade one long-term-support release at a time. Node 20 and older are end of life. 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. 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