redaxios VS documentation

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.

Have you heard about Feature-Sliced Design? I have personally found it extremely helpful as the project grows larger, though it can have a bit of a learning curve

In our case, the current folder structure resembles Feature-Sliced Design:

Feature-slice design is the one and only correct solution imho

(https://feature-sliced.design/)

for large spa I recommend https://feature-sliced.design/

There are many more benefits of using feature sliced design which are well documented in the docs. I highly recommend you to check it out and learn new ways of organizing your frontend project.

Hi, I use feature-sliced design for big or middle spa. Excellent solution for scalability! https://feature-sliced.design/

Ссылка на офф сайт.

You can also see a way around this restriction in "DDD, Hexagonal, Onion, Clean, CQRS, ... How I put it all together" and Feature Sliced.