Re:Yarn registry was down
by jessaustin on Friday May 25, 2018 @07:23PM
(#17158990)
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". This is an example of "every level of indirection can fail". [EDIT: removed unfounded speculation that CF wasn't necessary for yarn's requirements.]
[ Parent
| on HN ]
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-392...
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.
Re:Yarn registry was down
by foobarbazetc on Friday May 25, 2018 @07:53PM
(#17159164)
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.