wretch VS ky

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.

ky (3KB fetch-wrapper) has interceptors (we call them hooks).

You could always try ky.

If you're looking for an alternative to `fetch` or `axios` try out https://github.com/sindresorhus/ky. If you're looking at server-state management then I agree with react-query

Ky is a relatively new Javascript package that can be used for making asynchronous HTTP requests from the front end of a web application. It’s built on top of the native Fetch API with a simpler syntax and additional functionality.

Here is link number 1 - Previous text "ky"