Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Node.js, PHP and APIs

Create React App says Node is too old, and npm will not run on the new one

ErrorYou are running Create React App. Create React App requires Node 14 or higher.

Short answer

The shell is running an old Node.js that is below the version Create React App needs. Install a current LTS release with nvm, open a new terminal, confirm node -v, and run npx create-react-app again. Remove any old global create-react-app first.

  • Applies to Node.js 22, nvm 0.41, npm 10, Ubuntu 24.04
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Print the versions the shell actually uses. The Node version is the one in the error, not the one you think you installed.

    node -v
    npm -v
    which -a node
  2. 2Match what you see, then jump to its fix

    1. 1node -v prints a version below 14, for example v10.19.0The Node.js on your PATH is older than the tool needsFix
    2. 2nvm install finished, yet node -v in a new terminal still shows the old versionnvm installed the new version, but the shell does not use itFix
    3. 3The same tool runs every time instead of the latest oneAn old global create-react-app is installedFix

What does the error look like?

  • You are running Create React App. Create React App requires Node 14 or higher.
  • npm does not support Node.js v10.19.0

Cause 1 of 3

The Node.js on your PATH is older than the tool needs

1Check

The Create React App guide asks for Node 14 or newer on the development machine. The error is only reading node -v.

node -v

2Fix

Install nvm, open a new terminal so the command exists, then install and select the current LTS release.

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.41.0/install.sh | bash
# close this terminal, open a new one, then:
nvm install --lts
nvm use node

3Verify

node -v now prints a current version and the old error is gone.

node -v
npx create-react-app my-app

Confirmed by github.com

Did this fix it?

Cause 2 of 3

nvm installed the new version, but the shell does not use it

1Check

nvm only changes the version for shells where it is loaded. In a new tab, run nvm use, or pin the version for the project with a .nvmrc file.

command -v nvm
cat .nvmrc

2Fix

Add a .nvmrc to the project root so nvm use and nvm install pick the version without arguments.

echo "lts/*" > .nvmrc
nvm install
nvm use

3Verify

node -v shows the version nvm just selected.

node -v

Confirmed by github.com

Did this fix it?

Cause 3 of 3

An old global create-react-app is installed

1Check

The Create React App docs advise removing a global install so that npx fetches the latest version.

which create-react-app

2Fix

Uninstall the global package, then run it through npx.

npm uninstall -g create-react-app
npx create-react-app my-app

3Verify

npx downloads and runs the tool without the Node version error.

ls my-app/package.json

Confirmed by create-react-app.dev

Did this fix it?

How do I stop it coming back?

  • Pin the Node version per project with .nvmrc and an engines field in package.json.
  • Do not use the Node package from an old system repository for development; use nvm or the official installer.
  • Create React App is deprecated; for a new app, look at a framework from the React docs instead.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.