Consider deprecating registry.yarnpkg.com?

[jamiebuilds]

Opening this to discuss moving to registry.npmjs.org now that they've moved to Cloudflare.

Assuming we want to deprecate the Yarn registry (which seems to be the correct assumption), we need a plan for how to do it because a lot of infrastructure now depends on it.

For starters, we can never ever get rid of registry.yarnpkg.com completely. We shouldn't break those systems that depend on it, and it costs nothing so why would we not just leave it in place permanently.

Also, we cannot switch the registry config over outside of a major version as there are many CI systems that whitelist registry.yarnpkg.com and would break if it was switched.

However, we can start recommending that people change their Yarn configs to the npm registry immediately and start outputting deprecation warnings. Then in Yarn 2.0 we can switch the default registry over.

We could also consider putting something inside yarn.lock which configures the preferred registry and for new yarn.lock files we can use the non registry.

[arcanis]

Edit I changed my view, cf below.

You have a valid point, now that npm moved to Cloudflare we can reasonably expect a speed improvement, so using our mirror isn't that important (I personally feel motivated when I see our little stat page going up, but I agree this isn't a reason to keep the thing around if it doesn't benefit the users).

However as you mentioned we'll always have to keep the registry around, so I don't think there's any hurry to change things now (which doesn't mean we'll keep using it by default forever, but right now I'd prefer to focus on other things).

What I think we should do:

• Implement for the v2 the mecanism that will allow us to remove the registry host from the lockfiles (yarn.lock should not include base registry(http://registry.npmjs.org) #3330). This is something we wanted to do anyway, so that's great! I'll move the task in the v2 project, and if someone wants to tackle this, let me know.

• Once people start using the v2, their lockfiles will be progressively rewritten to not contain any host. Then, in a later release (not necessarily a major one), we'll then be able to toggle the default registry without requiring any change to the lockfile itself.

[BYK]

Once people start using the v2, their lockfiles will be progressively rewritten to not contain any host. Then, in a later release (not necessarily a major one), we'll then be able to toggle the default registry without requiring any change to the lockfile itself.

I think this will still be a breaking change due to whitelisting in CI environments. Is there a good reason to keep the proxy?

[jamiebuilds]

Yeah, it doesn't matter what is in the yarn.lock, it will be a breaking change because in some CI environments requests to registry.npmjs.org will fail

[g-plane]

I have created a module to help us convert the registry of yarn.lock file: https://github.com/g-plane/convert-registry