Pooya Parsa

Hi. Currently no giget doesn't supports this. In first next steps, you would be able to clone a local `.tar.gz` archive.

Support for https landed with #129. For this, we need something almost similar to support `file://` protocol provider and instead of fetching, using filesystem read. (PR welcome!)

The fix is merged to the main branch via #407 it will be released with the next minor sorry for inconvenience.

Thanks for making issue. Honestly i tend to agree with you. It is always easier to find relevant config files from `~/.config` (also cache from `~/.cache` etc). Main tricky part...

Nice idea to introduce new utils, we could call them `*userConfig()`

@Aareksio is well explained, ofetch is stateless by design. However, i see good use cases for stateful cookie (most importantly for testing), therefore made new proposal (~> #435). With stateful...

Thanks for PR. I was thinking of same solution too. I agree it is needed but (sadly) means 1) we allow patching behavior of a standard primitive 2) adds small...

Interesting idea. I think somehow we should extract such metadata from tar archive. We use [node-tar](https://github.com/isaacs/node-tar) internally might be a way to retrieve commit id.

Thanks. Seems reading is not that hard even if node-tar does not supports, we can easily find comment header: (update we can: https://github.com/isaacs/node-tar#class-tarpax) ``` > head release.tar pax_global_header00006660000000000000000000000064143737264400014524gustar00rootroot0000000000000052 comment=8ddd2a4eb6045710c1bac9761e97152cf6af4b8a ```

I like the idea. Only thinking it might be more suitable for `$fetch.raw` where we return full object (data body, headers and now possibly new `headers`). Combining two different return...