Npm doesn't see the newest npm package version

Question

Hay,

I have some big problems with sub-dependencies.

I have react-test-renderer package which uses react-is package.

And the problem starts here. Because of react-is want to be installed on version 16.3.1

But when I want to install only "react-is@16.3.1" then npm tells me that package version is not existing:

Also tried "npm view react-is" command to view if that version already exist:

The funniest thing is that, when I go to the npmjs.com page and look for the react-is version, there is a version 16.3.1 published 8h ago:

And When I type npm install command I got an error about not existing react-is version:

When I use yarn install then I can simply choose the existing version and everything works correctly:

But I can't use yarn on the production and I need to solve it somehow by using npm.

Maybe have you some idea, how should I solve this?

Answer 1

I had a similar problem and found out through npm info x that npm-package x was not showing the expected latest version. I then found out that I had an .npmrc custom registry config that messed that up. Removing it, installing the package, and then using the .npmrc again solved the problem for me.

Answer 2

I also had this issue. I could see the latest version of my package correctly published but every attempt to npm install failed. For me the solution was to clear the cache using npm cache clean --force after which npm install worked. Hope this helps anyone else having same issue

Answer 3

I was having the same issue and then I found out I had a custom repository in the .npmrc file. Deleting it solved the issue.

Answer 4

I have the same bug right now. Just try to upgrade your version one more time (in your case to 16.13.2). This should solve the problem. Maybe something is going wrong during package publication with npm publish