DI issues with MongoDB Entity Manager

[threes-was-taken]

Hi all,

I'm working on a NestJS API and I'm facing a DI issue for the MongoEntityManager import in a provider of a dynamic module. To easier understand the problem, let's call the module CatsModule.

So in the CatsModule, we import the MirkoOrmModule and give the option contextName the value of CatsModule.name.

The dynamic module is a class with 2 methods, forRoot and forRootAsync. For simplicity, I used the general module notation.

@Module({
  imports: [
    MikroOrmModule.forRoot({
      ...,
      contextName: CatsModule.name,
      ...
  ],
  providers: [CatsProvider],
})
export class CatsModule {}

Now in a provider of CatsModule, CatsProvider, I inject the EntityManager, through the use of DI.

@Injectable()
export class CatsProvider {
  constructor(
    @InjectEntityManager(CatsModule.name) // annotation is imported from '@mikro-orm/nestjs' v5.1.7
    private readonly em: EntityManager, 
  ...){}
}

The issue I'm facing is the following:

Nest can't resolve dependencies of the CatsProvider ([other constructor parameters], ?). Please make sure that the argument cats_EntityManager at index [4] is available in the CatsModule context.

Potential solutions:
- Is CatsModule a valid NestJS module?
- If cats_EntityManager is a provider, is it part of the current CatsModule?
- If cats_EntityManager is exported from a separate @Module, is that module imported within CatsModule?
  @Module({
    imports: [ /* the Module containing cats_EntityManager */ ]
  })

I don't understand why I'm facing this issue since, when I look at the documentation on both MirkoORM and NestJS sites, I don't see any difference in my approach.

The npm versions installed:
@mikro-orm/core : 5.6.9
@mikro-orm/mongo : 5.6.9
@mikro-orm/nestjs : 5.1.7

Thanks in advance for any input!

[threes-was-taken]

Solved this. The issue wasn't coming from the package, just a stupid mistake.