Users appreciate the thoughtful dev tooling details in Bun's proposed builtin on-disk fetch cache for scripts and offer suggestions like grep-based debugging.
Based on 4 visible X reactions from 5 accounts; directional sample.
Ask a question below.
Published answers will appear here.
@jarredsumner the grep angle for agent debugging is the part I'd ship first. know a few people building agent infra who'd have opinions on the JSON vs sqlite tradeoff - want me to put you in touch? https://x.com/messages/compose?recipient_id=1766194375044804608&text=want+intros+to+agent+infra+folks+for+the+Bun+fetch+cache+idea
@jarredsumner I always like how Spring used method annotations/decorators to enable caching. Felt more composable, cleaner than other solutions I’ve seen. https://docs.spring.io/spring-framework/reference/integration/cache/annotations.html
@jarredsumner yeah i think ideally a folder of either json or.http files for each request. only hiccup might be binary data in post bodies or sse streams, but overall would be phenomenal for debugging
@jarredsumner Still haven't touched bun or sqlite but this is the kind of dev tooling detail that makes me appreciate how much thought goes into these runtimes.
I still want Bun to have a builtin on-disk fetch cache, for debugging & testing & avoiding rate limits in one-off scripts maybe multiple backends, one with a folder of json files so that agents can debug with grep
every time I write a script to pull data from github I get rate limited and yes I have a PAT + I am aware that I can write a fetch wrapper. But I shouldn’t have to. This is a really common thing. It should be builtin. needs a CLI flag to enable without editing each fetch() call
Users appreciate the thoughtful dev tooling details in Bun's proposed builtin on-disk fetch cache for scripts and offer suggestions like grep-based debugging.
Based on 4 visible X reactions from 5 accounts; directional sample.
Ask a question below.
Published answers will appear here.