http.cat VS wretch

Cats for other HTTP status codes can be found (or not found :-)) one level up

https://http.cat

Whenever we request data or services from a server, it can respond with status codes represented by numbers. You've probably heard of "404" which means "not found", but there are others like "201 - Created" and "500 - Internal Server Error." During one of my mentoring sessions, I was given a website that showcased all these status codes with kitten memes and a brief description. It was fantastic and helped me grasp each one of those statuses better.

import { Module, OnModuleInit } from '@nestjs/common' import { HttpModule, HttpService } from '@nestjs/axios' import { CatApi } from './cat-api.service' @Module({ imports: [ HttpModule.register({ // line A timeout: 1_000, maxRedirects: 2, baseURL: 'https://http.cat', }), ], providers: [ { provide: CatApi, useExisting: HttpService, // line B } ], exports: [CatApi], // line C }) export class CatApiModule implements OnModuleInit { constructor(private readonly httpService: HttpService) {} onModuleInit() { this.httpService.axiosRef.defaults.headers.common['Accept'] = 'application/json' } }

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.