'react-scripts' is not recognized as an internal or external command / react-scripts: command not found
node_modules is missing or broken, so the react-scripts binary isn’t available.
Exact message you may see
'react-scripts' is not recognizedreact-scripts: command not foundsh: react-scripts: not found
Seen on:
React
Meaning
Fresh clones need npm install. Corrupt installs or switching package managers can drop .bin links.
Common causes
- npm install not run
- Corrupted node_modules
- Mixed package managers (yarn.lock + package-lock)
⚡ Quick fix
- npm install (or npm ci)
- Delete node_modules and reinstall
- Consider migrating from CRA to Vite
Detailed fix by platform
React
rm -rf node_modules package-lock.json && npm install
How to diagnose
- Installed — node_modules/.bin/react-scripts exists?
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in React
- Objects are not valid as a React child Error: Objects are not valid as a React child
- No QueryClient set Error: No QueryClient set, use QueryClientProvider to set one
- Functions cannot be passed Error: Functions cannot be passed directly to Client Components unless you explicitly expose it by marking it with "use server".
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026