|
| ▲ | tommy_axle an hour ago | parent | next [-] |
| I wouldn't go that far. Right tool for the job as always. Axios offers a lot over fetch for all but the simplest use cases plus you get to take advantage of the ecosystem. Need offline, axios-cache-interceptor already exists. Sure you can do all of those things with fetch but you need more to go with it taking you right back to just using axios. Also is no one annoyed that you can't replay fetch like the xhr? Same with express: solves a problem reliably. |
|
| ▲ | seanp2k2 10 minutes ago | parent | prev | next [-] |
| jQuery is still useful too. May you never work in heathcare / government / defense where you need to support legacy browsers far past their expiration date. |
|
| ▲ | danpalmer 2 hours ago | parent | prev | next [-] |
| 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 2 hours ago | parent [-] | | Any 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) I guess a LLM can do as well. Although that's not something I'm quite ready to admit. | | |
| ▲ | 8n4vidtmkvmk an hour ago | parent | next [-] | | I'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. | |
| ▲ | whattheheckheck an hour ago | parent | prev [-] | | Keep developing it. Your taste and judgement matter |
|
|
|
| ▲ | jwilliams 2 hours ago | parent | prev | next [-] |
| I do "just use fetch" nowadays -- but I have to say, axios definitely has better ergonomics than fetch, especially for calling APIs. |
| |
| ▲ | sampullman 2 hours ago | parent | next [-] | | I drag a tiny fetch wrapper around with error/json handling, timeouts and basic interceptor support. It doesn't cover everything axios does but it's nice enough and I haven't had to touch it in a couple years. For reference: https://github.com/sampullman/fetch-api/blob/main/lib/fetchA... | |
| ▲ | nurettin 2 hours ago | parent | prev [-] | | When the vulnerability was announced, it took me two minutes to one-shot convert an entire legacy project from axios to fetch (it already wrapped api calls neatly), react cra to vite, update all dependencies, convert to deep imports to reduce bundle size and get zero npm warnings while fetching coffee. There is just no excuse to use it. |
|
|
| ▲ | chvid 2 hours ago | parent | prev | next [-] |
| ChatGPT in general recommends axios over fetch. (At least it did about 2 months ago) |
| |
| ▲ | internetter an hour ago | parent [-] | | This is why people still need to know how to write code and why it is asinine to have an LLM write code without a human reading it. Good developers should know what good code looks like and push back when what they're fed is wrong. |
|
|
| ▲ | ariwilson an hour ago | parent | prev | next [-] |
| What's wrong with Express? |
| |
|
| ▲ | koolba an hour ago | parent | prev [-] |
| What’s wrong with express? |
