New version of pkg is published but not getting shown

[paulmillr]

See https://www.npmjs.com/package/chokidar

I've published 3.3.1, but the page, curl json api, and npm all say only 3.3.0 is available.

If you enter chokida into the search box, you'll see version: 3.3.1.

Also happens to other people: https://twitter.com/itsmequinn/status/1206246890427297802

[damian-pastorini]

hi @paulmillr , I'm having similar issue with another package, it seems could be related to #557 but I'm not sure... hope this gets fixed soon, for me is been hours since I've pushed my new version 👎

[damian-pastorini]

hi @paulmillr , I just re-try by bumping into a new version and now I can see the 3 of them:
Version History
4.0.0-beta.5
a few seconds ago
4.0.0-beta.1
4 hours ago
4.0.0-beta.0
a day ago

If you are in a rush maybe that would help me as me.
Best,

[paulmillr]

Not in a rush, so this is a bad long-term solution. Needs to be fixed ASAP!

[sanusart]

Same thing. Published 3.8.0 and afterwards 3.8.1 (both successfully) in attempt of cache bust but no go. Still showing 3.7.0

Search also shows new versions but site and npm view stuck on 3.7.0

https://www.npmjs.com/package/react-dropdown-select

[curtisblanchette]

Same issue here with private packages, npm packages published

Successfully published:
 - @4iiz/authorizer@1.9.3
 - @4iiz/config@3.7.2
 - @4iiz/data@5.2.2
 - @4iiz/nucleus@6.2.1

Installing from registry

npm ERR! code ETARGET
npm ERR! notarget No matching version found for @4iiz/authorizer@^1.9.3
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 'nucleus-api'
npm ERR! notarget

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-12-16T00_04_17_807Z-debug.log

[devloco]

Same problem here.

The global search on npmjs.com shows the latest version. But when you click into it, the version shows an old version. And running npx create-react-wptheme foo uses the old version.

[rssk]

Same issue here and bump publishing did not help :-( Causing major headaches for deploys

[mefu]

Same problem, and I am publishing 20 packages at once from a lerna repo. Just bumping versions until npm gets it correctly for each of them is a major pain.

[lc-soft]

Same issue. I published a new version of my package an hour ago, but until now I have not been able to install it in production environment.

[BitHighlander]

I waited 2-3 hours and it never "just showed up". clearly a bug and the only way to get around is spam the crap out of npm with version bumps till you get lucky. (ive spent my whole day fighting this )

[beenotung]

seems to be the same issue with npm/npm#20574

I think it's about npm cache not being updated

[beenotung]

@BitHighlander the workaround is to refer the dependency has github format. e.g.:

  "devDependencies": {
    "mk-package": "github:beenotung/mk-package#master"
  }

[janryWang]

I also encountered the same problem, when can this problem be fixed?

[DanielRuf]

@beenotung this is not correct as this does something different. It picks the Git repo (not always in pkg.repository), uses Git to clone it and downloads everything from it.

This is not a valid solution or workaround. Also because dist is often not in there.

[ljharb]

I'm seeing the same with v1.0.1 of globalthis, and a few others.