Published package does not show up in the registry immediately

[egoist]

I just published a package, but it's been 5 minutes and npm is still returning the cached version.

Following screenshots are taken at the same time:

[egoist]

I'm closing this because now the package has been updated properly on npm registry, but I always need to wait for 5 to 10 minutes for the registry to actually update..

[egoist]

Re-opened because it happens again when I publish a new version..

[crash7]

Same here, private package, new versions are not showing up in the site or when we run npm install package

Update: now one of the versions I published 30 minutes ago is showing up.

[soldair]

thanks for letting us know. I'm taking a look at this issue for private packages still. hopefully ill have it sorted very soon

[shubhanshusingh]

I am facing same issue for private packages.Got the mail that it got published, but unable to install it somewhere else as it says target not found and displays list of older versions of package.

[fathyb]

Same here, public package parcel-plugin-typescript. Just published two versions (0.8.0-next.1 and 0.8.0-next.2) and I can't find them in the registry despite the confirmation mails.

[ef4]

I suspect the issue is affecting all namespaced packages, not just private ones, because we are waiting on several public namespaced packages to appear.

Example: @cardstack/authentication 0.7.10 was published successfully at 12:28 EDT (40 minutes ago at the time of this comment), and it's still not visible.

[soldair]

this should be resolved. if anyone is still not seeing a version they know should be there please contact support and ill look into it =)

[egoist]

hmm that seems to be resolved but some other issue happens here:

I just added egoist to the package vue-feather-icons, it's updated on the website itself but npm registry does not get updated..

[amorist]

same issue

[egoist]

I'm really frustrated that it's still not solved. I added egoist to package ream and the npm registry is yet updated after days of waiting..

[soldair]

\o please email support@npmjs.com if you have any issues that especially if its been days, we're happy to look into your specific issue

[oleics]

Same here: https://registry.npmjs.org/ac-json-apis should be 0.0.6, but is stuck at 0.0.5 since several hours

[rarkins]

@soldair FYI it's happening again big time

[schalkneethling]

Same here, on the packages view it shows the correct version but, when I go to the modules individual page, there is a version mismatch. Also, installing with npm i -D --save-exact <package-name> I do not get the latest version.

[schalkneethling]

The page listing the package now correctly reflects the latest version but, npm i still installs the old version. Progress, yay. Thanks!

[dawnerd]

Will this https://status.npmjs.org/incidents/3rjzvts6v98k get older publishes up to date?

npm show still shows old version - not matching site