crud VS axios

I've found you can move very fast with NestJS and NestJSX CRUD, which gives you all CRUD operations out of the box, just be careful to lock it down as much as possible https://github.com/nestjsx/crud

REST CRUD: https://github.com/nestjsx/crud

I used nestjsx-crud in the api we prepared. This library makes CRUD operations very easy. However, there is no support on the authorization side. That's why I made use of the accesscontrol library, which can be easily integrated with both nestjs and refine.

NestJS is a framework for building efficient, scalable Node.js server-side applications. With nestjsx/crud we can add CRUD functions quickly and effortlessly on this framework.

This is some good inspiration: https://github.com/nestjsx/crud

For example, when using the HttpModule module from @nestjs/axios we can use the dynamic module HttpModule.register() to configure our Axios instance. That module exposes a HttpService that has such configuration. But what if we want to have many Axios instances, each one with its own config and import everything in one module?

e.g. there's no reason in one of these systems where you couldn't just use Axios (or fetch) on its own to make outside requests. But instead, for no good reason, Nest wants to wrap Axios for you in a way that allows you to only really grab a single instance at a time. Which is not how Axios is meant to be used. This makes it so that you can't use the baseURL config option which is one of the most important options when constructing a client that's meant to work with a particular service. You could use a named injector but at this point there's no reason to not just pass around an instance other than Nest seemingly having this alternate pointless way of doing things. So basically, yes, in this case Nest pushes you into a pattern but that pattern isn't just ugly... it's inherently limiting to you while being more verbose and decreasing readability.

NestJs HttpModule