npx create-react-app prints a deprecation message or will not set up a new project
create-react-app is deprecated.Short answer
Create React App was deprecated by the React team in February 2025 and has no active maintainers. A new install prints a deprecation notice that points to React's framework list. Start new projects with a framework, or with Vite, and check that your Node.js version meets Vite's minimum.
Fix it fast
1Find out which cause you have
Read the message in full. If it says create-react-app is deprecated, the tool is not broken in your setup; it is retired for new apps. Also check your Node.js version.
node --version npm --version2Match what you see, then jump to its fix
What does the error look like?
create-react-app is deprecated.This error message will only be shown once per install.
Cause 1 of 2
Create React App is deprecated for new apps
1Check
React announced the deprecation, because the project has no active maintainers. It stays in maintenance mode, and a version was published to work with React 19.
node --version2Fix
Create the app with a framework, or with Vite for a plain client-side app. The React docs list Next.js, React Router and Expo as framework starters.
npm create vite@latest my-app -- --template react
cd my-app
npm install
npm run dev3Verify
The dev server starts and prints a local URL.
npm run devConfirmed by react.dev
Cause 2 of 2
Node.js is too old for the replacement tool
1Check
Vite documents the Node.js versions it needs. Compare yours with it.
node --version2Fix
Upgrade Node.js to 20.19 or newer, or 22.12 or newer, then scaffold again. Some templates may need a newer one.
# after upgrading Node.js with your usual tool
node --version
npm create vite@latest my-app -- --template react3Verify
The scaffold finishes without engine warnings.
node --versionConfirmed by vite.dev
How do I stop it coming back?
- Start new apps from the React docs page for new projects, which lists the current recommendations.
- Write the required Node.js version in the project README, so every machine uses a supported one.
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:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- WorkforceA field app, an admin console and a self-hosted Node.js server for push and reconciliation.
Related fixes
Web apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
AxiosError Network Error with code ERR_NETWORK in a React app
Network Error
ERR_NETWORK means the request produced no readable response.
4 causes, each with a fixWeb apps
Axios get works with a URL string but ignores the object passed as the second argument
The server log shows a GET with no query string
axios.get takes a URL and an optional config object.
3 causes, each with a fixWeb apps
Can't resolve '../axios' in a React project
Module not found: Error: Can't resolve '../axios'
A path that starts with ./ or ../ is a file path, not the axios package.
3 causes, each with a fixWeb apps
Axios returns 401 from a React app but the login works elsewhere
Error: Request failed with status code 401
A 401 means the server received the request without valid credentials.
3 causes, each with a fixWeb apps
An axios call never finishes when the API server stops answering
code: 'ECONNABORTED'
Axios has no timeout unless you give it one: the default is 0, which means wait forever.
3 causes, each with a fix