Nah. Facebook’s Yarn works as a client to the NPM registry with a different take on _how_ to obtain those packages. This is a WHOLE different registry that’s now also using the NPM registry as a place to fetch them from. Note that publishing a package… https://v2.jacky.wtf/post/b7216b92-0530-472c-a4f8-4ac032fdbcd8 …
-
-
Really? I could have sworn checking in like, the very earliest days, and there was no proxy? Maybe that was before launch...
-
There may have been really early on, but that would have been before the Yarn CLI ever used it, and pre open source. Fastly definitely returned a HTTP status code because the "http://registry.yarnpkg.com " host wouldn't have been accessible with just a CNAME.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 