redaxios VS wretch

Once you start to handle all the corner-cases of the fetch, you will find that you don't want to repeat the boilerplate each time you call network, so you will write some wrapper around the fetch or use redaxios library from Jason Miller, which provides axios-like API on top of fetch so it weights only 800 bytes, which is nice. But then you might need the axios interceptors which redaxios do not implement and if your application upload files and you want to track the upload progress with ProgressEvent, the fetch does not support that, only XMLHttpRequest does, on which the original axios is based. And after you write all your custom wrappers around fetch and upload wrappers around XMLHttpRequest, you might reconcider the original statement, that axios library is obsoleted.

If you love Axios, but don’t love that it’ll add 11kb to your bundle, Redaxios is a great alternative, that uses the same API as Axios, but in less than 1kb.

Axios is another great, and very popular, solution for clean data fetching. It is a bit larger (10kb gzip vs 2kb gzip), so if kb size is important to you (I would argue it typically should be) redaxios is a great option too

Then you get redaxios.

There's a neat library called https://github.com/developit/redaxios that implements almost all the Axios API, but as a wrapper around fetch instead.

As for your very last comment, for those who can’t part from axios’ API, try redaxios which is just a super thin wrapper around fetch().

If you want use fetch but with Axios API, small size(~1KB), I suggest you checkout redaxios from Preact creator.

In conclusion, whether you choose axios, fetch, or an alternative like wretch, your focus should be on writing clear, maintainable, and robust code. Understanding the strengths and weaknesses of each tool will empower you to make informed decisions and build applications that are not only functional but also resilient and enjoyable to develop.

This package does it quite nicely https://github.com/elbywan/wretch

One newer option, which is a very thin wrapper around Fetch much like Redaxios, is Wretch. Wretch is unique in that it largely still feels like fetch, but gives you helpful methods for handling common statuses which can chain together nicely:

It would be better with a link to kick things off so boomers can choose to read about it instead https://github.com/elbywan/wretch

For ajax, I never use Axios anymore, I always use Wretch these days.

Wretch Wretch on the other hand takes the function chaining approach. It split common error types into separate helper methods so you don't need to result in an interceptor every time

You might be interested in Wretch, it's very lightweight and has a nice middleware facility.