What is the task of NestJS?

Question

Node.js

Are we really reducing the amount of boilerplate code or just following the architecture imposed by the framework?

After reading the docks, there was a doubt that only the second goal is being realized. We follow the architecture of the framework, in return we agree that we will not change the framework in the future, because the framework code grows deep into the business logic.

On the other hand, a large proportion of vacancies require knowledge of NestJS, which indicates wide popularity, including among team leaders and seigneurs. Please explain to the jun, what is the grandeur of Nest and why experienced comrades use it, if you can get by with a conditionally hexagonal architecture, and give routing and request processing to a lightweight express that can be replaced with koa\hapi\%framework_name% with one click?

Answer 1

just following the architecture imposed by the framework?

You talk like it's bad.

manage conditionally hexagonal architecture

The architecture lies a level above the framework.

and give routing and request processing to a lightweight express,

Just to avoid writing extra code.
Nest allows code to be written more declaratively with annotations, controllers, IoC, and a request processing pipeline.
Declarative code is easier to read than imperative code.