Observation on Nx TS Workspaces and NestJS Module Resolution Challenges

[ak274]

I've observed a issue with NestJS applications in an Nx workspace using TypeScript Workspaces. NestJS manages dependencies through its own module system, utilizing the imports and exports arrays within the @Module decorator. When a module is imported into another module's imports array and then re-exported, the consuming module may fail to recognize this dependency.

This occurs because Nx's static analysis doesn't detect dependencies managed internally by NestJS's Dependency Injection system. Consequently, the build process fails, as the workspace doesn't acknowledge the module as a known dependency.

[junior-zip]

This behavior highlights a gap between Nx's static analysis and NestJS's dynamic module system. It's important to manually declare dependencies in project.json to ensure proper detection and avoid build issues. Correct?

[Wykks]

This could be fixed with this change f117119
(Unreleased as of today)