Yarn support
Snotax opened this issue · comments
Did you drop the updates / support of the yarn package or did you just forget to push it there ?
We are currently using this package via yarn :D
Thank you in advance :D
Hey, I thought 1.1.1 fixed the issue... What's the current problem for you?
I'm sorry, I didn't quite write it correct.
I have no problem with the library as it is. I just saw (https://yarnpkg.com/package/axios-cache-interceptor) still has v 1.0.1 and I wondered if you are still going to update the yarn package of the library in the future or only the npm one.
Sorry for the inconvenience.
Hey @Snotax, I was using yarn publish before v1.1 but now I migrated to pnpm. I have no plans to come back to use yarn. I have no idea on how to publish to the yarn registry manually. Would this be a problem for you?
@arthurfiorette Hmm yes... this would be a problem for us. We're using react-native with a yarn monorepository. We would have to migrate to another caching solution.
Unless you guys are using a self-hosted yarn cache, just changing the package registry url to any other would be enough. And in the self hosted case, just ask someone to put it in there.
I actually never used or configured something on yarn registry itself, so I'm not sure why it stopped fetching from the npm registry.
@arthurfiorette Thank you for your insights. We will try to configure it this way. I will hit you up again if anything failes :D
Casually passing by: Yarn registry is actually just a CNAME on the npm registry, so there shouldn't be any difference with npm.
Well, now I'm confused... I do not have any idea on why there's only up to 1.0.1 on yarn.
Oh right, on the website search, it doesn't show new versions. May be related to this yarnpkg/berry#5451 issue (TLDR: Yarn uses an algolia index that seems not up to date)
Thats it, thanks @Embraser01 for the explanation.