'react-scripts' is not recognized as an internal or external command
To resolve the issue of 'react-scripts' not recognized, ensure react-scripts is installed with this command:
If this doesn't do the trick, you may have corrupted dependencies. To clean up, remove node_modules and package-lock.json, then reinstall them.
Make sure your scripts section of package.json looks like this:
To ensure changes are reflected, open a brand new terminal.
Troubleshooting the issue
If you encounter a 'react-scripts not recognized error, check if the dependency is listed under "dependencies". If it's AWOL, then npm install react-scripts --save should bring it back.
When this doesn't cut it, you got to consider other factors. Possibly permissions, outdated package managers, or an corrupted npm cache are causing hiccups.
Compatibility Check
Sometimes being incompatible isn't limited to just relationship. It could also be your package manager and your Node.js not being bffs. Make sure the versions you are using are:
- NPM version: >= 5.5.1
- Node.js version: >= 9.3.0
If not, update Node.js to be 'the one' using:
Window users fear not, you can switch node versions with nvm-windows.
Cleaning Up, Step By Step
Before jumping to conclusions, let's clean house - starting with clearing your possibly corrupted npm cache using the npm cache clean --force followed by a npm rebuild.
In some cases, the project may need a fresh start, just like all those diet plans we abandon on day 2. Reclone the project, and see if it solves the error:
Deep Dive: Troubleshooting
If the basic shenanigans don't fix the problem, roll up your sleeves, it's time for deep troubleshooting:
Scripts & Environment
Your react-scripts test scripts and dependency environment may need a check-up. Make sure React scripts and all your dependencies are up-to-date and compatible.
Going Manual and Cleaning Up
As the last solution, doing a manual npm install react-scripts@latest --save or yarn add react-scripts --save might be needed. Similarly, cleaning up your installation using rm -rf node_modules package-lock.json && npm install might also do the trick.
Beyond the first solution
Understanding what causes react-scripts errors can help pinpoint broader issues within your development environment, and following these steps can make you the debugging master.
Was this article helpful?