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
-
git based semver matching is another, albeit much slower, preexisting option. adding semver ranges for tarball deps would require some coordination but doesn't seem entirely implausible (some Well Known URL based off the tarball URL).
Yeah that's another option. Strong git support was actually a requirement for of the Yarn partner teams (who no longer actually uses it...). I did a lot of hacks to make it as fast as possible, including use `git archive` which allows you to request a git remote for a tarball.
