## You might of seen something like:

```
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @babel/types@^7.9.6.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
```

> [similar issues here](https://github.com/babel/babel/issues?q=label%3A%22i%3A+npm+cache%22+is%3Aclosed)

Check if the package for which `npm` throws an error is published by searching [on the npm website](https://www.npmjs.com/). 

For example: [`@babel/types`](https://www.npmjs.com/package/@babel/types)

![image](https://user-images.githubusercontent.com/588473/82709443-99cdb980-9c4e-11ea-839f-01bfb5929185.png)

Here you can validate that the version on the website is up to date. If it's there, *then it was correctly published* on our end, but for some reason your package manager client doesn't find it, likely due to using a proxy. In this case, we won't be able to do anything on our end.

## Proxies

> This seems to happen right after a publish, as the cache's need to update.

If you are using a proxy (Nexus) for the npm registry (maybe it's used by your company, or you are using it because your country blocks the main npm registry), then it's likely that it has cached the old version of the package and it isn't loading the new one. If you can, try clearing the proxy's cache. Otherwise, you will have to wait until the cache is automatically updated (it might take a few hours, or even days).

If you are not using a proxy, or if it isn't a caching problem, please report the issue to [npm](https://github.com/npm/cli/issues/new/choose) instead of the Babel repo!