4 ms·

Issue is here: https://github.com/yarnpkg/yarn/issues/5885 https://github.com/yarnpkg/yarn/issues/5885 The problem is that npm just migrated their registry to

Issue is here: https://github.com/yarnpkg/yarn/issues/5885 https://github.com/yarnpkg/yarn/issues/5885 The problem is that npm just migrated their registry to use CloudFlare. Yarn already used CloudFlare, and had https://registry.yarnpkg.com https://registry.yarnpkg.com CNAME'd to https://registry.npmjs.org https://registry.npmjs.org. CloudFlare has a security restriction that one CloudFlare account cannot have DNS records pointing to another CloudFlare account, so npm moving to CloudFlare broke yarn's existing CNAME to npm's registry (thus breaking yarn).

jessaustin 8y ago
Sorry but this is kind of funny. It would have been easy for the default value in the app to have been "https://registry.npmjs.org" https://registry.npmjs.org". This is an example of "every level of indirection can fail". [EDIT: removed unfounded speculation that CF wasn't necessary for yarn's requirements.]
- foobarbazetc 8y ago
  CF DNS is pretty good for a free service. Lots of annoyances to be sure but saying they’re not focused on it is kind of wrong. This is actually an issue with the CDN portion not the DNS portion.
- judge2020 8y ago
  Based on the (recent) comment on the issue [0], they use the Cloudflare proxy instead of an actual CNAME /and use workers to do yarn-specific changes on the edge / (see below). [0]: https://github.com/yarnpkg/yarn/issues/5885#issuecomment-392215450 https://github.com/yarnpkg/yarn/issues/5885#issuecomment-392...
  - deleted 8y ago
    [deleted]
  - deleted 8y ago
    [deleted]
  - arcatek 8y ago
    I work on Yarn. The message you're quoting is from the npm CTO. We don't do yarn-specific changes. The main reason we're using a mirror is because it was massively faster than directly querying the npm registry when Yarn got released. The difference decreased during the past year I think, but Cloudflare was still a bit ahead in most scenarios.
foobarbazetc 8y ago
You can CNAME across CF accounts but you can’t CNAME a proxied record to another proxied record.
ryanworl 8y ago
Fun fact: you actually used to be able to do this and it caused some security problems! There are probably zones out there that are still able to do it today from back when it was allowed.
- orf 8y ago
  What security problems?
  - asadlionpk 8y ago
    I wonder that too. Circular cnames?

jessaustin 8y ago

Sorry but this is kind of funny. It would have been easy for the default value in the app to have been "https://registry.npmjs.org" https://registry.npmjs.org". This is an example of "every level of indirection can fail". [EDIT: removed unfounded speculation that CF wasn't necessary for yarn's requirements.]

foobarbazetc 8y ago
CF DNS is pretty good for a free service. Lots of annoyances to be sure but saying they’re not focused on it is kind of wrong. This is actually an issue with the CDN portion not the DNS portion.
judge2020 8y ago
Based on the (recent) comment on the issue [0], they use the Cloudflare proxy instead of an actual CNAME /and use workers to do yarn-specific changes on the edge / (see below). [0]: https://github.com/yarnpkg/yarn/issues/5885#issuecomment-392215450 https://github.com/yarnpkg/yarn/issues/5885#issuecomment-392...
- deleted 8y ago
  [deleted]
- deleted 8y ago
  [deleted]
- arcatek 8y ago
  I work on Yarn. The message you're quoting is from the npm CTO. We don't do yarn-specific changes. The main reason we're using a mirror is because it was massively faster than directly querying the npm registry when Yarn got released. The difference decreased during the past year I think, but Cloudflare was still a bit ahead in most scenarios.

foobarbazetc 8y ago

You can CNAME across CF accounts but you can’t CNAME a proxied record to another proxied record.

ryanworl 8y ago

Fun fact: you actually used to be able to do this and it caused some security problems! There are probably zones out there that are still able to do it today from back when it was allowed.

orf 8y ago
What security problems?
- asadlionpk 8y ago
  I wonder that too. Circular cnames?