etsy-ts VS wretch

Honestly, the hardest thing to figure out is the OAuth2 Handshake, token scopes, and how to update the rolling token/retry requests that fail from that. It's much more annoying to configure than the previous iteration, but not really much different than a lot of 3rd party APIs. I dug through this repo: https://github.com/Granga/etsy-ts/tree/master/src and have extended it for my needs, mostly just adding convenience functions as my application is only concerned with my shop and the repo is more generic.

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.