0

I see multiple people asking the same questions about trying to run create-react-app, which then claims an older version of Node is running, even though I uninstalled it via nvm multiple times. Here's one example of my attempts to choose a later version of node I have already installed:

Mac:react me$ nvm install v16.13.2
v16.13.2 is already installed.
Now using node v16.13.2 (npm v8.1.2)
Mac:react me$ npx create-react-app@latest my-app
You are running Node 12.14.1.
Create React App requires Node 14 or higher. 
Please update your version of Node.
Mac:react me$ npm uninstall -g v12.14.1

up to date, audited 1 package in 317ms

found 0 vulnerabilities
Mac:react me$ nvm use 16.13.2
Now using node v16.13.2 (npm v8.1.2)
Mac:react me$ npx create-react-app@latest my-app
You are running Node 12.14.1.
Create React App requires Node 14 or higher. 
Please update your version of Node.
Mac:react me$

I'm running High Sierra, so can't update to the latest/greatest verison of node, but as I understand it, I shouldn't have to. How do I fix this so I can actually run create-react-app on my system? Many thanks in advance for your help.

jimiayler
  • 674
  • 2
  • 11
  • 27
  • Sounds like `npx` isn't using the `nvm` Node version. It's probably a `PATH` ordering issue – Phil Feb 14 '23 at 01:16
  • Does this answer your question? [npx runs a node version which does not exist on my machine](https://stackoverflow.com/q/64512568/283366) – Phil Feb 14 '23 at 01:17
  • @Phil Sorry to say no - I ran `node -p process.execPath` and it returned `/Users/me/.nvm/versions/node/v16.13.2/bin/node`. Running `/usr/bin/env node -v` returned `v16.13.2`. – jimiayler Feb 14 '23 at 01:27
  • What about `which npx`? It should be in the same path as `node`. For me it's `~/.nvm/versions/node/v16.14.2/bin/npx` – Phil Feb 14 '23 at 01:57
  • Does `brew list | grep 'node'` return any results? (if you had installed Node via Homebrew) – Wesley LeMahieu Feb 14 '23 at 03:48

1 Answers1

0

The only solution that worked for me was to both remove node and nvm via CLI and manually. nvm isn't needed on my system anymore, as previous versions of node were for legacy projects I'm no longer working on.

The CLI solution (largely using Homebrew) is discussed many places on SO, including here, and manually also many places online, notably here.

jimiayler
  • 674
  • 2
  • 11
  • 27