This is totally off topic, but I am glad to see this here. Nest.js seems really powerful on the surface, when you start reading their docs [0] everything makes sense at first. But the deeper you go, the more it sets in that the complexity introduced by its "magic" results in very little being easily reasoned about. Just look at the process for building a GraphQL API [1], for example, it starts out simply enough then goes off the deep end. Decorators, dependency injection and providers within providers all the way down.
I went down that rabbithole when I had to set up Graphql with federation. The reason it seems complicated is because they're attempting to fit bootstrap processes of different libraries into their own IoC style by writing tiny wrappers.
You end up with large blocks of config in ugly decorators but what they're doing is trying to supply that config to the underlying libs.
I consider Nestjs docs to be among the best written docs in the node community. Virtually everything you need is in there.
[0]: https://docs.nestjs.com [1]: https://docs.nestjs.com/graphql/quick-start