Ever wondered why developers are going for Axios over fetch? As we are aware both are the means to deal with HTTP or XMLHttp requests, Both are capable of making all types of API calls (get, post,put.. etc.). Both are based on Promise API which is native to ES6. But what are the major points to be noted?
First, .fetch() has a two-steps process while handling JSON data. The first makes the actual request and then the second is to call the .json() method on the response.
const url = 'https://api.spotify.com/v1/artists/0OdUWJ0sBjDrqHygGUXeCF'
fetch(url)
.then(response => response.json())
.then(data => console.log(data));
As a good developer, our main aim is to minimize the code. Axios deals it with a single line.
const url = 'https://api.spotify.com/v1/artists/0OdUWJ0sBjDrqHygGUXeCF'
axios.get(url).then(response => console.log(response));
Second is, Error handling. Logically if .fetch() gets an error it would enter the .catch() block and should return but, it eventually executes the next then() in chain. see below:
But Axios handles it, the way it is expected.
it returns from catch, no more .then() chaining.
So, .fetch() method is a great way of getting HTTP requests native in ES6, but there are just few gotchas, that could be dealt by these third party libraries.
Nice and quick overview, Ash! And just in time, thanks!
--
I wanted to learn more about
fetchpromise failing reasoning after your post. To share, heres a quote from MDN fetch:So, "bad news" is still "news" in
fetchimplementation.--
UPD: also,
axiosandfetchhave different cancellation API.