I've never run into a case where I've needed to use axios in almost a decade of being a professional web developer. It's mostly been an annoyance whenever I've come into contact with it, and replacing it with fetch() calls would've solved those issues.

Besides that, axios is a dependency for functionality that is already built into the web platform.

[–] [email protected] 1 points 4 months ago (1 children)

Unless you need to account for compat (DoD, gov't contractors), easy cancellation (e.g. polling is necessary vs pubsub), upload progress (e.g. progress bars for large uploads), or better errors (axios throws on server errors, fetch, by default, replies OK).

It's also nicer to configure - though I suppose you can just build classes for each fetch client on the frontend. Middleware - in particular, is easier in axios for advanced auth flows.

Native fetch is great, but saying no one uses one of the most installed (per weekly) packages on npm is just outright wrong.

Then again, this is a weird hill for me to die on so I'll leave it. The confidence of your statement was just...strange. And for some reason I was compelled to comment.

[–] [email protected] 1 points 4 months ago

Those are all just a compilation of special cases...

I didn't say nobody uses it. There are so many projects using it, and I think no professional should be defaulting to including axios in their project unless absolutely necessary.