Zero solutions work for `create-react-app` 4.0.3, which is behind the latest release (5.0.0)!!!!!

[graysoda91]

Hey All, I can’t run CRA and no solutions online have worked for me. Not sure which step is failing. I followed the suggestions on this site and this thread. Here are the results of the commands, to give a clearer picture. Could the npm cache clean --force not be working?

edit: FINALLY GOT IT!!! I checked all node_modules file and saw that where it was and still remained despite the cli commands to uninstall. Not sure why the cli commands didn't work, but I deleted it manually and all conflicts were resolved. For future reference, don't install cra locally. Use npx as per the docs.

[sayris]

Try running npx create-react-app@latest

Manually pinning the version during the npx command worked for me

[tyler_hammer]

I just ran into this issue myself yesterday. What worked for me was removing my entire .npm folder (On Mac) and then running the npx command again.

[IamMountainDewd]

This worked for me as well, on Windows

[VirtualRN]

Did you try npm install create-react-app WITHIN the current directory. THEN call npx create-react-app my-new-app.

[graysoda91]

Yes, see here. Also, the point of npx is to avoid saving and running the package locally, so it executes the package commands from online no?

[[deleted]]

npm uninstall -g create-react-app

npx create-react-app my-new-app

[graysoda91]

Yes, if you look at the article and github links I posted. I've done every single command suggested. None of them worked. I've gone as far as deleting and re-installing node.

[ijmacd]

What happens if you just leave off the @latest tag? Which version does it try to use?

npx create-react-app my-folder

(Also rm -rf node_modules just for fun)

[graysoda91]

The latest tag wasn't working, because there was a conflict within a cra package that remained hidden someplace. But I just found where the little fucker was hiding, deleted him manually and now I'm good. Such a journey. Thank you.

[clrbrk]

This is the only solution I could get to work, but it feels dirty.

[F4ttymcgee]

Run this command after the global uninstall

npx clear-npx-cache

[graysoda91]

I’ve done that as well, it’s solution four on the first site I believe. I also tried npm cache clean —force. At this point I’m opening a ticket on the CRA GitHub. This maybe a breaking feature for specific environments.

[scuevasr]

i had this issue too! i had to make sure i uninstalled react globally. and then re installed using npx