it's been more than a few months since I looked at this aspect but I think I found a way of lazy loading the required data without having to clone. even a depth 1 clone can be bandwidth and storage heavy for many repositories. I'll let you know how I get on.

Replies (2)

I think I need to be slapped in the face. I added support for displaying the readme but only for github right now. I planned to use `git archive` but wasm-git and isomorphicgit don't support it. any form of `git clone` is too bandwidth inefficient. I'm not sure its worth prioritising adding another backend proxy (other than though sveltekit) to use the standard git client to achieve this at this point. The other option is identifying the git server software used and targeting the readme's 'raw' url like I'm doing with github.
All I wanted was that people could use self-hosted or niche git servers without having to feel like they were leaving a lot behind on GitHub, but now you're making GitHub the standard again. Not a big deal, but meh. Why is git clone inefficient?