I still use on axios over fetch. Mainly because fetch doesn't have abort function. axios implements cancelable promise proposal that didn't go though TC39
Tho it has been a while since I checked TC39 status on fetch
Re:D3.js 5.0 is out
by thomasfoster96 on Friday March 23, 2018 @05:22AM
(#16656324)
Fetch is a Web API, not an ECMAScript language feature, so TC39 doesn’t have much to do with it. They do do Promises though and Cancellation is a Stage 1 proposal [0], so it’s more than a year away from standardization at best.
WHATWG handles Fetch and their spec[1] was updated seven days ago.
[0] https://github.com/tc39/proposals/blob/master/README.md [1] https://fetch.spec.whatwg.org
Re:D3.js 5.0 is out
by mhagemeister on Friday March 23, 2018 @02:00AM
(#16655479)
Fetch requests do support cancelation for a while now through `AbortController`. See: https://developers.google.com/web/updates/2017/09/abortable-...
Re:D3.js 5.0 is out
by igvadaimon on Friday March 23, 2018 @07:13AM
(#16656820)
Which doesn't work even in Chrome.
Re:D3.js 5.0 is out
by mattwoodnyc on Friday March 23, 2018 @01:31AM
(#16655340)
I also choose Axios over Fetch for now. I had the following post that made the case - https://medium.com/@thejasonfile/fetch-vs-axios-js-for-makin...
Thoughts?
It's been great to rely on a standard function, than any of the libraries to make http requests.