hyperstack VS axios

This is exactly what you get for free in Hyperstack (https://hyperstackjs.io/), which I open sourced yesterday ;)

I built a framework for building products for startup, just open sourced this week: https://hyperstackjs.io

You can build everything with Hyperstack: https://hyperstackjs.io, which uses Sequelize under the hood

Ok, in the https://hyperstackjs.io/ On the stack overflow community it redirects to the one in ruby

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