4 ms·
If you want a fully built out network layer, with auth, logging, monitoring, policies, etc, then `fetch` doesn't really help. Axios and other libraries provide
by danpalmer 6mo ago
If you want a fully built out network layer, with auth, logging, monitoring, policies, etc, then `fetch` doesn't really help. Axios and other libraries provide much more for building that sort of framework.
- internetter 6mo agoAny sufficiently competent typescript developer can build out an adhoc wrapper (that just inherits the type definition and passes along whatever it is passed after altering it however needed) in under a hour. It doesn't scale in the sense that you don't expose a configuration, but config as code is king. (Source: have built out much more scuffed variants of this than the one I just described like https://github.com/boehs/ajar https://github.com/boehs/ajar) I guess a LLM can do as well. Although that's not something I'm quite ready to admit.
- whattheheckheck 6mo agoKeep developing it. Your taste and judgement matter
- 8n4vidtmkvmk 6mo agoI've wrapped fetch a few times but i don't think I'd blame someone if they got tired of wrapping it and wanted a consistent interface across all the projects they work on.
- interstice 6mo agoAh yes ad hoc, the best way to write fundamental utilities underpinning every fetch your app makes.
- internetter 6mo agoWrapping fetch is not rocket science