npm ERR! 404 'coa@^2.0.2' is not in the npm registry.

[vivex]

Summary

When i am trying to install expo-cli globally or trying to run expo with npx getting the following error:

➜  ~ npx expo init fitnest
npx: installed 359 in 104.384s
This command requires Expo CLI.
Do you want to install it globally [Y/n]? Y
Installing the package 'expo-cli'...
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/coa/-/coa-2.1.3.tgz
npm ERR! 404
npm ERR! 404  'coa@^2.0.2' 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 'expo-cli'
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!     /Users/viveksoni/.npm/_logs/2021-12-25T07_40_28_190Z-debug.log
Installing Expo CLI failed. You can install it manually with:
  npm install --global expo-cli

Environment

npx expo diagnostics also failing with above error, tried with node 10, 12, 14 (lts) on macos big sur

Please specify your device/emulator/simulator platform, model and version

NA

Error output

No response

Reproducible demo or steps to reproduce from a blank project

run npm install --global expo-cli

[brentvatne]

following up from the related thread: veged/coa#99

likely your machine was caching 2.1.3, this is a bug on the npm side and not expo-cli. @DanielRuf mentioned that it might have been in our lockfile, which would make sense if you were installing it by cloning this repo but npx will not use any lockfiles.

so, this is likely an intermittent issue caused by caching and the npm registry. if you still have this issue, try npm cache clean --force or disable / reset any npm proxy/cache server that you're using

[DanielRuf]

Ah, right. Could be local caches which means that this pc was likely affected.

For yarn: yarn cache clean