Cli: New version of pkg is published but not getting shown

64

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

paulmillr picture paulmillr  路  15 Dec 2019

Most helpful comment

7

Verified, our missing packages come back again 馃憦

Keith-CY picture Keith-CY  路  16 Dec 2019

All comments

0

hi @paulmillr , I'm having similar issue with another package, it seems could be related to https://github.com/npm/cli/issues/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 picture damian-pastorini  路  15 Dec 2019
1

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,

damian-pastorini picture damian-pastorini  路  15 Dec 2019
0

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

paulmillr picture paulmillr  路  15 Dec 2019
1

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

sanusart picture sanusart  路  15 Dec 2019
1

Same issue here with private packages, npm packages published

```lerna http fetch PUT 200 http://registry.npmjs.org/@4iiz%2fnucleus 3933ms
Successfully published:


Installing from registry

npm ERR! code ETARGET
npm ERR! notarget No matching version found for @4iiz/[email protected]^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
```

curtisblanchette picture curtisblanchette  路  16 Dec 2019
1

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.

2019-12-15 19_08_53

2019-12-15 19_08_58

devloco picture devloco  路  16 Dec 2019
0

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

rssk picture rssk  路  16 Dec 2019
3

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.

Mefu picture Mefu  路  16 Dec 2019
0

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.

lc-soft picture lc-soft  路  16 Dec 2019
3

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 )

BitHighlander picture BitHighlander  路  16 Dec 2019
0

seems to be the same issue with https://github.com/npm/npm/issues/20574

I think it's about npm cache not being updated

beenotung picture beenotung  路  16 Dec 2019
-7

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

  "devDependencies": {
    "mk-package": "github:beenotung/mk-package#master"
  }
beenotung picture beenotung  路  16 Dec 2019
0

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

janryWang picture janryWang  路  16 Dec 2019
4

@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.

DanielRuf picture DanielRuf  路  16 Dec 2019
0

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

ljharb picture ljharb  路  16 Dec 2019
-2

+1

SoloJiang picture SoloJiang  路  16 Dec 2019
0

same issue with [email protected]

wssgcg1213 picture wssgcg1213  路  16 Dec 2019
5

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

uditalias picture uditalias  路  16 Dec 2019
-1

+1

tommanger picture tommanger  路  16 Dec 2019
-1

+1

amitbiton01 picture amitbiton01  路  16 Dec 2019
2

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 !

jeremyben picture jeremyben  路  16 Dec 2019
-2

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 [email protected]:

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 :)

fwouts picture fwouts  路  16 Dec 2019
-3

+1
image-1

image-2

Topthinking picture Topthinking  路  16 Dec 2019
2

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!!! 馃帀馃帀馃帀

shilman picture shilman  路  16 Dec 2019
0

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.

nicolo-ribaudo picture nicolo-ribaudo  路  16 Dec 2019
0

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

cihadhoruzoglu picture cihadhoruzoglu  路  16 Dec 2019
0

For me it started working again a few minutes ago.

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

farfromrefug picture farfromrefug  路  16 Dec 2019
0

Same issue, 1 took over 16 hours.

rjpkuyper picture rjpkuyper  路  16 Dec 2019
0

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

Subash picture Subash  路  16 Dec 2019
1

Same issue for me, private org.

boh1996 picture boh1996  路  16 Dec 2019
0

Same issue, the new version get shown when i publish a beta version锛寃hile the tarball is still not found

ClarkXia picture ClarkXia  路  16 Dec 2019
0

Same issue for me

chenshuai2144 picture chenshuai2144  路  16 Dec 2019
0

馃敟

doxiaodong picture doxiaodong  路  16 Dec 2019
0

same issue with our project!
redo npm publish

npm ERR! 403 Forbidden - PUT https://registry.npmjs.org/@vaadin%2fvaadin-core - You cannot publish over the previously published versions: 15.0.0-alpha9.

do npm install

npm ERR! code ETARGET
npm ERR! notarget No matching version found for @vaadin/[email protected]
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
ZheSun88 picture ZheSun88  路  16 Dec 2019
2

Same issue for my private repo

RamdhasUeikattan picture RamdhasUeikattan  路  16 Dec 2019
-2

+1

robinfehr picture robinfehr  路  16 Dec 2019
-2

+1

dontepsu picture dontepsu  路  16 Dec 2019
5

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

jsomsanith-tlnd picture jsomsanith-tlnd  路  16 Dec 2019
3

@jsomsanith-tlnd not really - I pinged twitter, and neither there, not here did any NPM employee answer. The fuck they charge 10k$ for? (https://www.npmjs.com/products) Is it for 20 hours of downtime of an important feature?

paulmillr picture paulmillr  路  16 Dec 2019
0

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

Keith-CY picture Keith-CY  路  16 Dec 2019
0

[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

ZheSun88 picture ZheSun88  路  16 Dec 2019
7

Verified, our missing packages come back again 馃憦

Keith-CY picture Keith-CY  路  16 Dec 2019
0

Seems to be happening again.

benmcginnis picture benmcginnis  路  19 Dec 2019
0

Seems to be happening again.

With which package for example?

DanielRuf picture DanielRuf  路  19 Dec 2019
0

It's a private org package

benmcginnis picture benmcginnis  路  19 Dec 2019
0

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.....

Gippsman2017 picture Gippsman2017  路  2 Feb 2020
0

@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 picture beenotung  路  2 Feb 2020
0

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

beenotung picture beenotung  路  2 Feb 2020
0

@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.

DanielRuf picture DanielRuf  路  2 Feb 2020
0

@DanielRuf I get you, I was off topic

beenotung picture beenotung  路  2 Feb 2020
0

@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

stephanebruckert picture stephanebruckert  路  20 Feb 2020
0

@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 picture DanielRuf  路  20 Feb 2020
0

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.

DanielRuf picture DanielRuf  路  20 Feb 2020
0

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:

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

ruyadorno picture ruyadorno  路  20 Feb 2020
0

I seem to be having this issue right now 馃槙

ledlamp picture ledlamp  路  5 May 2020
0

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 picture DanielRuf  路  5 May 2020
0

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

DanielRuf picture DanielRuf  路  5 May 2020
0

It's updated now

ledlamp picture ledlamp  路  6 May 2020