If the npm registry disappeared. How quickly could it be rebuilt? (Without the cooperation of npm inc). Is anyone still mirroring the registry? The migration away from couchdb and the registry software being closed source would make it difficult.
-
Show this thread
-
Replying to @sebmck
Wouldn't the yarn registry be able to pick up the slack?
2 replies 0 retweets 6 likes -
Replying to @joshmanders
Yarn registry had always been a reverse proxy with CloudFlare. npm switched to CloudFlare though and fucked it up because CloudFlare disallows proxying to themselves. They took control of our registry DNS, which is why we no longer have any usage statistics.
2 replies 2 retweets 26 likes -
Replying to @sebmck
Dang that sucks. So now it's all back in control of npm, inc.
1 reply 0 retweets 6 likes -
Replying to @joshmanders
I mean, we can seize control of it. We just won’t be able to point it at npm. Yarn still accounts for like 40% of registry traffic so it’s hard finding that sort of capacity.
2 replies 0 retweets 8 likes -
Replying to @sebmck @joshmanders
I wonder whether
@the_jsf has a contingency plan in mind.1 reply 0 retweets 4 likes
Sebastian Retweeted Mikeal Rogers
Sebastian added,
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 