I've encountered a strange issue. Nest is flagging a missing dependency in a service, but only when that service is Injected by multiple other services.
cleaning.module.ts
@Module({
imports: [
//Just a few repos
],
providers: [
ServicesService,
...
AreasService,
RoomsService,
...
],
controllers: [
...
],
exports: [
ServicesService,
...
AreasService,
RoomsService,
...
]})
services.module.ts, areas.module.ts, and rooms.module.ts all have similar structures.
@Module({
imports: [CleaningModule],
providers: [],
controllers: [],
exports: []
})
rooms.service.ts
constructor(@InjectRepository(Room) private readonly repo: Repository<Room>, private areasService: AreasService) { }
services.service.ts
constructor(@InjectRepository(Service) private readonly repo: Repository<Service>, ... private roomsService: RoomsService) { }
This setup leads to the following error message:
ERROR [ExceptionHandler] Nest can't resolve dependencies of the RoomsService (RoomRepository, ?). Please make sure that the argument dependency at index [1] is available in the CleaningModule context.
It seems that AreasService is somehow missing, even though it should be provided by the CleaningModule.
The odd thing is, if I eliminate the injection of RoomsService in the constructor of ServicesService, everything works perfectly fine. The reasoning behind this behavior eludes me...