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
I'm not trying to do anything. This tweet isn't even about that and is completely unrelated. This is something you can do today, that circumvents the registry. You aren't creating your own. Just hosting tarballs for your own packages.
-
-
Correct. But it's not a fork or a mirror. It's just reusing the same capabilities that npm clients offer today.
- 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.
he/him 