Force cache clean

[pastelsky]

Force cache clean

[pastelsky]

Hi @Kelin2025. We do not cache package searches that don't have an explicit version specified — for eg - a search for react is not cached, but one for [email protected] would be. Discovery of new versions should be near instantaneous as far as I can remember.

The error in the screenshot might be caused by #43 (comment) .

Let me know if this is still a issue.

[Kelin2025]

I will check it on next version update

[nksfrank]

We where publishing fix where we where adding react as a peerDependency to our package.

But searched on our new version to soon, before it had been fully published, getting a MissingDependencyError

[pastelsky]

What do you do see after publish?

…

On 09-Feb-2018 4:17 PM, "Niklas Frank" ***@***.***> wrote: We where publishing fix where we where adding react as a peerDependency to our package. [image: image] <https://user-images.githubusercontent.com/7352072/36024018-b795307a-0d8e-11e8-95c5-e12ca8133501.png> But searched on our new version to soon, before it had been fully published, getting a MissingDependencyError [image: image] <https://user-images.githubusercontent.com/7352072/36023925-6ef7c120-0d8e-11e8-8981-84a93a5e68ed.png> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#44 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIiCH42BzIo2ynLyOlMH9kpg92ZoVhw1ks5tTCIkgaJpZM4Rd2TT> .

[nksfrank]

the MissingDependencyError result is from after publish.
Our package is published now and in use over at our codesandbox example: https://codesandbox.io/s/w0orz7j5p8

[nicolasdelfino]

1.9.2 was released shortly after, this version first showed the same error (MissingDependencyError), then after a refresh it continued with resolving / bundling & minifying but sadly it got stuck on "calculating file sizes" .

[pastelsky]

Just checked, we have short time cache (a few hours) for package searches that don't include a version. However, when one searches with an explicit version, this should not happen.

[ardalanamini]

@pastelsky I'm searching an explicit version but still get the error PackageVersionMismatchError

here's the link: https://bundlephobia.com/result?p=@foxify/[email protected]

[pastelsky]

The yarnpkg registry seems to be taking some time to reflect this newly published version. Bundlephobia's search depends on its presence.

…

On Thu, May 30, 2019, 12:29 AM Ardalan Amini ***@***.***> wrote: @pastelsky <https://github.com/pastelsky> I'm searching an explicit version but still get the error PackageVersionMismatchError here's the link: ***@***.******@***.*** — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#44?email_source=notifications&email_token=ACEIEHYRVNA4GN6BYIL2S5DPX3HBRA5CNFSM4ELXMTJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWQKLKA#issuecomment-497067432>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACEIEH4QUPAITIIAM6NS3QDPX3HBRANCNFSM4ELXMTJQ> .

[ardalanamini]

Maybe you should reconsider your registry choice, 'Cause my package's version still isn't available in yarnpkg and this could happen to other packages too

[pastelsky]

This should be fixed in the next release. We'll now use npm's official registry to resolve versions. Thanks!