Besides being relatively new, it seems to have basic things you need.
It’s been baseline since March of 2017.
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.
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.
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.
Years and years of trying to find a better web framework when php exists
“Oh just use axios and await async the promise to make http calls”
Statements dreamed up by the absolutely deranged
Just use php and curl
What professional actually recommends axios?
What’s wrong with axios? Quite a bold claim. Do you just want to sound smart?
What’s wrong with
fetch()?Nothing, as far as I can tell. Besides being relatively new, it seems to have basic things you need.
So what’s wrong with axios? Asking the inverse doesn’t answer my question.
It’s been baseline since March of 2017.
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.
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.
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.
lol, nice addition.
No. There’s just rarely a legitimate reason now to use axios. It shouldn’t be the first recommendation on which to build your API fountain.