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.

[SoloJiang]

+1

[wssgcg1213]

same issue with rax-slider@1.1.2

[uditalias]

+1
same issue here, published private scoped packages, npm confirmation received but old version is still the latest one.

[tommanger]

+1

[amitbiton01]

+1

[jeremyben]

Same thing. Yet you cannot republish the same version, hoping to force it, you'll get a 403 "You cannot publish over the previously published versions".

So our new version is in there somewhere.
I get the eventual consistency thing, but this is a little too eventual !

[fwouts]

Same with react-screenshot-test, I'm still waiting for v1.3.1 to appear after 2.5 hours.

FYI I got the following automated reply from support@npmjs.com:

Our support hours are Monday through Friday, 9:00AM - 6:00PM PST, excluding US holidays.

It's currently Monday 2:10AM PST, so hang on for another 7 hours :)

[Topthinking]

+1

[shilman]

Have been trying to publish the Storybook monorepo all day ... still not working. Excerpt from https://github.com/storybookjs/storybook/blob/next/CHANGELOG.md 😭

## 5.3.0-beta.30 (December 16, 2019)

Failed NPM publish

## 5.3.0-beta.29 (December 16, 2019)

Failed NPM publish

## 5.3.0-beta.28 (December 16, 2019)

Failed NPM publish

## 5.3.0-beta.27 (December 16, 2019)

Failed NPM publish

## 5.3.0-beta.26 (December 16, 2019)

Failed NPM publish

UPDATE: Fixed!!! 🎉🎉🎉

[nicolo-ribaudo]

Unfortunately this isn't a new issue. It has already happened to us different times when publishing Babel, and so far the only "fix" has been to wait a few hours.

[cihadhoruzoglu]

We have same issue, it's already been 3 hours

[farfromrefug]

For me it started working again a few minutes ago.

EDIT: talked too fast, only some updates are being seen

[rjpkuyper]

Same issue, 1 took over 16 hours.

[Subash]

Same issue here as well, packages published to a private org are also not showing up.

[dontepsu]

+1

[jsomsanith-tlnd]

(I think npm folks understood that there is an issue, stop spamming with the useless (+1))

[Haprog]

Related official status/incident posts:

• https://twitter.com/npmstatus/status/1206578392641916929
• https://status.npmjs.org/incidents/lg9535dl2ff3?u=fxyzgpnvyr9w

[Keith-CY]

I've released 2 versions today and there's one out of four packages lost each time.

[ZheSun88]

[status] Monitoring: The issue has been identified and outstanding publishes should begin to resolve in the public registry. We are monitoring the situation to ensure that the resolution works as intended.

Should be okay now, our publish is visible now

[Keith-CY]

Verified, our missing packages come back again 👏

[benmcginnis]

Seems to be happening again.

[DanielRuf]

Seems to be happening again.

With which package for example?

[benmcginnis]

It's a private org package

[Gippsman2017]

This appears to be broken again, anyone else with the same issue
npm search node-red-contrib-redlink returns version 2.0.2 as does the website.
However the https://www.npmjs.com/package/node-red-contrib-redlink return 2.0.4, this causes npm to install an old version and node-red-flows to use the old version.....

[beenotung]

@DanielRuf if the repo maintainer setup CI to build the package, e.g. into 'dist' branch or semver tag, it is still a resilient fallback in case npm is not working.

If the repo maintainer doesn't do that, consumer could fork that ...
Or tried to publish to npm in another name and hope it works ...
But both way will require extra effort to keep the fork in sync with the upstream

[beenotung]

I'm talking about 'hacks' instead of 'fixes' because we cannot touch the infra of npm

[DanielRuf]

@beenotung not sure to which reply from me you are referring to.

People can also use the Git URL but this will use git to clone it.

[beenotung]

@DanielRuf I get you, I was off topic

[stephanebruckert]

@Gippsman2017 also still having this problem. Couldn't get the latest version from the cmd line while it was correctly shown in the npmjs.com UI, after doing npm publish on 3 different private repos on these dates:

• 2020-02-10 18:37
• 2020-02-13 17:13
• 2020-02-17 09:45

Re-publishing immediately after usually works, but it's not a good long term solution

[DanielRuf]

@stephanebruckert did you already report that to the npmjs support? That usually means that there is some cache somewhere (local or on npmjs side or the registry parts) which may not be uptodate.

[DanielRuf]

I think this issue here is resolved for a long time already and your issue is another / new case.

In this thread everyone of the 41 involved people will get a notification for updates here which is not that great.

[ruyadorno]

Agreed, thanks for point that out @DanielRuf 👍

I'm going to close this issue since it was related to the December incident which have been fixed since then.

@stephanebruckert you can reach out to registry support on the appropriate channels:

• https://www.npmjs.com/support
• support@npmjs.com
• https://twitter.com/npm_support

Thanks to the aforementioned 41 involved people for helping surfacing the problems and providing updates 😊

[ghost]

I seem to be having this issue right now 😕

[DanielRuf]

I seem to be having this issue right now confused

@ledlamp please open a new issue with all relevant details and the exact error message that you get.

[DanielRuf]

Also please check if you have published to the correct registry and cleared the browser cache.

[ghost]

It's updated now

[4KDA]

Now some problems :-(

[DanielRuf]

@4KDA please see https://status.npmjs.org/

The same is probably published there: https://twitter.com/npmstatus

Please do not comment here since this issue is already closed, was about an old incident and now ~40 people got a notification.

@ljharb we should lock this thread here.