npx create-react-app aborting installation

Describe the bug

hello there I am creating a new app in reactjs for hooks I tried using npx create-react-app hooksapp I am getting below error ⤵

Did you try recovering your dependencies?

• npm install -g npm@latest
• npm install

Environment

Environment Info:

current version of create-react-app: 3.4.0 running from C:\Users\krish\AppData\Roaming\npm\node_modules\create-react-app

System: OS: Windows 10 10.0.18363 CPU: (8) x64 Intel® Core™ i5-8250U CPU @ 1.60GHz Binaries: Node: 12.14.1 - C:\Program Files\nodejs\node.EXE Yarn: Not Found npm: 6.14.7 - C:\Program Files\nodejs\npm.CMD Browsers: Edge: 44.18362.449.0 Internet Explorer: 11.0.18362.1 npmPackages: react: Not Found react-dom: Not Found react-scripts: Not Found npmGlobalPackages: create-react-app: Not Found

(paste the output of the command here.)

Steps to reproduce

(Write your steps here:)

1.npx create-react-app hooks

Actual behavior

npx create-react-app painthook

Creating a new React app in C:\Users\krish\painthook.

Installing packages. This might take a couple of minutes. Installing react, react-dom, and react-scripts with cra-template…

npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/@typescript-eslint%2Feslint-plugin - Not found npm ERR! 404 npm ERR! 404 ‘@typescript-eslint/eslint-plugin@^2.10.0’ is not in the npm registry. npm ERR! 404 You should bug the author to publish it (or use the name yourself!) npm ERR! 404 It was specified as a dependency of ‘react-scripts’ npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, http url, or git url.

npm ERR! A complete log of this run can be found in: npm ERR! C:\tmp\nodejs\npm-cache_logs\2020-08-06T10_13_42_796Z-debug.log

Aborting installation. npm install --save --save-exact --loglevel error react react-dom react-scripts cra-template has failed.

Deleting generated file… package.json Deleting painthook/ from C:\Users\krish Done.

Reproducible demo

• 

[superjose]

Hi @krishnadevz !!! There have been numerous reports here on the issue list. Please, avoid creating any more of these issues. It’s an npm issue https://status.npmjs.org/

[EmmanuelTheCoder]

I have resolved it. It had to clean my cache. npm cache clean --force