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
-
Both clients have first-class support, caching etc. Registry packages are just tarballs after all. This would actually be faster as there's no need to hit a JSON endpoint to get the package URL
5 replies 0 retweets 21 likesShow this thread -
Replying to @sebmck
Wouldn’t this only be faster if the package has no deps (or if they’re all bundled)? They couldn’t prefetch in parallel. I would expect that such a system would result in fewer bigger deps, like what we see in golang, java, or in js pre-2009.
2 replies 0 retweets 2 likes
Replying to @izs
Yeah it would. I should have clarified, I was way too vague. The packages I’m imagining this for are top-level and wouldn’t have any external dependencies.
1:52 PM - 30 Mar 2019
0 replies
0 retweets
4 likes
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 