[Bug]: No matching version found for @babel/helper-plugin-utils@^7.18.6

[Inchill]

💻

• Would you like to work on a fix?

How are you using Babel?

Other (Next.js, Gatsby, vue-cli, ...)

Input code

npm ERR! code ETARGET
npm ERR! notarget No matching version found for @babel/helper-plugin-utils@^7.18.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 
npm ERR! notarget It was specified as a dependency of '@babel/plugin-proposal-class-properties'
npm ERR! notarget 

Configuration file name

No response

Configuration

No response

Current and expected behavior

I just run npm install command to install a cli package in private registry and always get this error, though it shows 7.18.6 is available.

Environment

• Babel version: 7.16.0
• Node version: 10.15.0
• Npm version 6.4.1
• OS: Mac OS 12.4

Possible solution

No response

Additional context

No response

[babel-bot]

Hey @Inchill! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite.

[babel-bot]

Hi @Inchill!
This seems to be an issue caused by a package that you are not able to download. You can verify that the package is available using the npm website: for example, https://www.npmjs.com/package/@babel/types?activeTab=versions is the URL for @babel/types (replace @babel/types in the URL with the package you want to check). If you see zero downloads don't worry: npm can take up to a few days to display the downloads count, but this does not mean that the package is not available.
Here are some things you can try:

1. Please check if there is a stale proxy or cache between you and npm (this is the most likely cause and it is common in corporate networks).
2. Visit https://status.npmjs.org/ to see if the current npm is working properly.
3. See https://gist.github.com/hzoo/df94af2d2ec48696e683b772c775aa67

[nicolo-ribaudo]

This is a bug with your private registry!