NestJS builds a module definition before assembly; Vona never has a module definition to build.
Anyone who has used NestJS knows forRoot() . When wiring a database, a queue, or a config module, almost every third-party package offers a static method that takes your options:
@Module ( { imports : [ TypeOrmModule . forRoot ( { type : 'mysql' , host : 'localhost' } ) ] , } ) export class AppModule { }
Enter fullscreen mode
Exit fullscreen mode
At first this looks like "the advanced way to write a module." After a while it becomes clear that it is a patch β a patch over the premise that a module definition must be known in advance.
Coming to Cabloy/Vona, many people look for the equivalent: components, configuration, and scaffolding are all there, but there is no such thing as a "dynamic module." The reason is not that it has not been built yet. It is that the problem it solves does not exist in Vona .
1. What a Dynamic Module Actually Does
Start with the minimal form.β¦