Unable to install newly published package version

I published react-navigation-tabs@0.8.4 and went to install it and was unable to with either yarn or npm (6.4.1). I confirmed on the package page that it was published successfully. It has now been about 20 minutes since I published 0.8.4, and about 30 since I published 0.8.3, neither of them are available.

The version seems to be available when I look it up in the registry by hand, but it seems pacote keeps fetching from cache:

7 http fetch GET 200 https://registry.npmjs.org/react-navigation-tabs 14ms (from cache)
8 silly registry:manifest no matching version for react-navigation-tabs@0.8.4 in the cache. Forcing revalidation
9 http fetch GET 304 https://registry.npmjs.org/react-navigation-tabs 104ms (from cache)
10 silly fetchPackageMetaData error for react-navigation-tabs@0.8.4 No matching version found for react-navigation-tabs@0.8.4

Not sure what’s happening there exactly, but while testing it started working already.

Thanks for the response @larsgw! It’s still not working on my end.

That’s weird :confused:. Probably just some caching, but still… weird. And annoying. If you visit the registry entry in the browser do you see 0.8.4 already? Because I did, before the CLI started working on my end.

strange, I’m still seeing 0.8.2 as the latest in the browser

1 Like

I also tried it from my phone and see 0.8.2 there as well. A colleague in another country entirely sees 0.8.2 too.

When I view it with a VPN (Canada) I do see 0.8.2, so it seems like a regional caching thing. However, I’m not on the npm team so this is out of my control.

it seems to have resolved itself now

This is due to a temporary caching issue on the registry side. It has since been resolved and the original cause is being investigated more thoroughly.

1 Like

Hi. It looks like the problem is back… I’ve just published v2.1.3 of a package, it appears on the website and with npm view, but it’s impossible to install. Same issue as @brentvatne

1 Like

I can also confirm the issue is back.

1 Like

I’m also experiencing this issue.

vue@2.5.22 has been released about 1 hour ago.

When I go to https://registry.npmjs.org/vue I can see version 2.5.22.

My npm on the other hand cannot find this version, apparently because it is using a cached version of that page:

283 silly install loadCurrentTree
284 silly install readLocalPackageData
285 http fetch GET 200 https://registry.npmjs.org/vue-template-compiler 15ms (from cache)
286 silly pacote version manifest for vue-template-compiler@2.5.22 fetched in 18ms
287 http fetch GET 200 https://registry.npmjs.org/vue 27ms (from cache)
288 silly registry:manifest no matching version for vue@2.5.22 in the cache. Forcing revalidation
289 http fetch GET 304 https://registry.npmjs.org/vue 122ms (from cache)
290 silly fetchPackageMetaData error for vue@2.5.22 No matching version found for vue@2.5.22
291 timing stage:rollbackFailedOptional Completed in 1ms
292 timing stage:runTopLevelLifecycles Completed in 1708ms
293 verbose type version
294 verbose stack vue: No matching version found for vue@2.5.22

I would actually be happy if it would just use a cached but consistent set of packages, but apparently npm got the information from somewhere that 2.5.22 is available and now it is trying to install it (and fails) and it won’t settle for 2.5.21.

This problem went away when I upgraded npm from 6.4.1 to 6.7.0.

2 Likes

happening again for me, this time with expo-font@2.1.0-alpha.1

edit: seems to have resolved itself after a few minutes

This is happing with me too, I’ve publish one lib and is no longer being updated:

npm view react-edp-components

➜   npm i react-edp-components@4.1.0
npm ERR! code ETARGET
npm ERR! notarget No matching version found for react-edp-components@4.1.0
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! A complete log of this run can be found in:
npm ERR!     /Users/rcardoso/.npm/_logs/2019-04-30T18_37_05_207Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/Cellar/node@8/8.11.3_1/bin/node',
1 verbose cli   '/usr/local/opt/node@8/bin/npm',
1 verbose cli   'i',
1 verbose cli   'react-edp-components@4.1.0' ]
2 info using npm@5.6.0
3 info using node@v8.11.3
4 verbose npm-session 5390eb4c2568d2ad
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 http fetch GET 304 https://registry.npmjs.com/react-edp-components 197ms (from cache)
8 silly registry:manifest no matching version for react-edp-components@4.1.0 in the cache. Forcing revalidation
9 http fetch GET 304 https://registry.npmjs.com/react-edp-components 47ms (from cache)
10 silly fetchPackageMetaData error for react-edp-components@4.1.0 No matching version found for react-edp-components@4.1.0
11 verbose type version
12 verbose stack react-edp-components: No matching version found for react-edp-components@4.1.0
12 verbose stack     at pickManifest (/usr/local/Cellar/node@8/8.11.3_1/lib/node_modules/npm/node_modules/pacote/node_modules/npm-pick-manifest/index.js:65:11)
12 verbose stack     at fetchPackument.then.packument (/usr/local/Cellar/node@8/8.11.3_1/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/manifest.js:52:18)
12 verbose stack     at tryCatcher (/usr/local/Cellar/node@8/8.11.3_1/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
12 verbose stack     at Promise._settlePromiseFromHandler (/usr/local/Cellar/node@8/8.11.3_1/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
12 verbose stack     at Promise._settlePromise (/usr/local/Cellar/node@8/8.11.3_1/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)
12 verbose stack     at Promise._settlePromise0 (/usr/local/Cellar/node@8/8.11.3_1/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
12 verbose stack     at Promise._settlePromises (/usr/local/Cellar/node@8/8.11.3_1/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:693:18)
12 verbose stack     at Async._drainQueue (/usr/local/Cellar/node@8/8.11.3_1/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:133:16)
12 verbose stack     at Async._drainQueues (/usr/local/Cellar/node@8/8.11.3_1/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:143:10)
12 verbose stack     at Immediate.Async.drainQueues (/usr/local/Cellar/node@8/8.11.3_1/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
12 verbose stack     at runCallback (timers.js:810:20)
12 verbose stack     at tryOnImmediate (timers.js:768:5)
12 verbose stack     at processImmediate [as _immediateCallback] (timers.js:745:5)
13 verbose cwd /Users/rcardoso/pdm/edp/PLUGINS/mainreactmenu/react
14 verbose Darwin 18.2.0
15 verbose argv "/usr/local/Cellar/node@8/8.11.3_1/bin/node" "/usr/local/opt/node@8/bin/npm" "i" "react-edp-components@4.1.0"
16 verbose node v8.11.3
17 verbose npm  v5.6.0
18 error code ETARGET
19 error notarget No matching version found for react-edp-components@4.1.0
20 error notarget In most cases you or one of your dependencies are requesting
20 error notarget a package version that doesn't exist.
21 verbose exit [ 1, true ]

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.