ROUTER_MODULE_GUIDE

NestJS RouterModule routes go missing because controllers inside nested imported modules are not recognized. You must declare controllers directly in the presentation module registered with RouterModule.register() to ensure proper route prefixing and route discovery.

Configure your presentation module to register its controllers directly, then wire it into RouterModule.register() with the desired path prefix. This ensures controllers are properly recognized and prefixed in dynamic multi-package NestJS applications.

Yes, NestJS RouterModule supports dynamic module routing by enforcing that controllers are declared directly in the registered module. This architectural pattern separates library and presentation modules to fix route discovery issues in multi-package apps.

The correct modular routing architecture requires declaring controllers directly within the module registered to RouterModule, rather than relying on nested imports. This enforces proper route prefixing and ensures all presentation module routes are discovered.

No, NestJS RouterModule does not recognize controllers inside nested imported modules for path prefixing. You must declare controllers directly in the specific module registered with RouterModule.register() to ensure correct route discovery and prefix application.