In my previous article, “Deep Insights Into JavaScript’s Fetch API”, I discussed the basics of the Fetch API. But it’s worth acknowledging that fetch() isn’t consistently an ideal solution, and there…

BtrProg offers insights into software development best practices, algorithms, and data structures, providing tutorials, articles, and coding challenges to help developers improve their programming skills. By exploring BtrProg's curated content, developers can learn about algorithmic problem-solving techniques, data manipulation strategies, and code optimization methods for writing clean, efficient, and maintainable code. Whether you're preparing for coding interviews, honing your competitive programming skills, or simply sharpening your coding prowess, BtrProg offers resources to level up your programming game.

Better Programming

Fetch() is part of a JavaScript window-object method within the Fetch API. It is built in, so users don’t have to install it. Users can avoid boilerplate and write cleaner, more succinct code in Axios. Axios has some advantages, like protection against cross-site request forgery (CSFR) attacks.

Why JavaScript Developers Should Prefer Axios Over Fetch

One of those cases where frontend devs are obsessed with a library which uses the default api on the back just because in some cases is “easier” just like jQuery was easier to use than javascript. I actually don’t get why the obsession, I’ve found lots of trouble to make a request that fetch made it simpler.
Also is kind of a deceit that for the fetch request does not use new js shortcuts and for the same example with axios that would’ve been the same length or even larger uses new js shortcuts of use of functions, callbacks, etc

I don’t trust any article with “should” in it’s title

Not a wise thing to compare an out of the box solution which requires 0 effort for integration vs a full blown library developed over the years.
Its like saying JS devs should stop using Array methods and use lodash utilities which has many more utilities written for Arrays.

I disagree with the overall mentality to keep using libraries for built in vanilla functions. Yes, if you work on a big project where you need extra functions where “fetch” lags behind “axios”, or you need to support 10+ year old browser, then absolutely, use axios. However what I see all the time, is the developers use axios on tiny projects, where all they do is make a simple get request that “fetch” can easily handle. Stop using massive libraries for every single function unless it’s really necessary.