he/him 
This is not a thought experiment. This is a real concern and possibility. The community would not be prepared.
Show this thread
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.
-
-
-
Also, would this even be legal? When you create an npm account you give them the rights to distribute your work. If a new registry spins up, they wouldn’t have those rights. Maybe you would have to filter based on known licenses specified in package.json?
Show this thread
End of conversation
New conversation -
-
-
Wouldn't the yarn registry be able to pick up the slack?
-
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.
- 4 more replies
New conversation -
-
-
The problem are not the modules. The problem are the user credentials and permission to publish a given module. No one can replicate those, as they are private.
-
true, but not having those for a while won't destroy millions of dollars. That can be mitigated over time.
- 14 more replies
New conversation -
-
-
A lot of companies has a their own registry and act as a proxy with npm. So no prob.
-
Yeah but it just proxies and saves the packages that go through it. A lot of those systems aren’t mirroring everything.
End of conversation
New conversation -
-
-
We have the entire registry and all its history. In fact, you can look at it in RunKit’s filesystem. The way it works is the node_modules are in a temporal virtual fs, where the top level folders are timestamps representing the state of the registry at that millisecond.
-
You can see it here: https://runkit.com/tolmasky/module-fs-requiring-immutable …
- 2 more replies
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.