he/him 
If you had to install an npm package by URL, instead of by registry name, would you mind? eg. $ npm install https://website.com/package.tgz $ yarn add https://website.com/package.tgz
Show this thread
-
A distributed system of DNS servers would still have human friendly names. A distributed package naming system with consensus and checksums sounds great. Expecting users to enter full URLs, let alone checksums, seems very optimistic.
It would only be for installation. I’m not talking hypotheticals, you can do it today. URLs are human-readable, and everyone copy+pastes from tutorials+GitHub anyway, no typing required. https://twitter.com/sebmck/status/1112056018802884608?s=21 …
This Tweet is unavailable.
-
-
Ah so you mean that package.json (or equivalent, or even the source in the Go-like Deno model) would use full URLs? How would the user initially populate this upon first adding a dependency? If no typing URLs is required, would there still be a naming registry?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
eh, I can't remember the last time I copy/pasted from a GitHub repo for a dependency name, especially when starting up a new project. yarn add express typescript tslint @types/express @types/node becomes WAY more cumbersome with FQDNs
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.