MikroOrmModule.forRootAsync ignores MikroOrm provider useFactory function

[mikro-orm]

MikroOrmModule.forRootAsync ignores MikroOrm provider useFactory function

[JhonFuenzalida]

I had the same error and I solved it by changing the type to drive

import { Module } from '@nestjs/common';
  import { ConfigModule, ConfigService } from '@nestjs/config';
  import { MikroOrmModule } from '@mikro-orm/nestjs';
  import { PostgreSqlDriver } from '@mikro-orm/postgresql';
  
  @Module({
    imports: [
      MikroOrmModule.forRootAsync({
        imports: [ConfigModule],
        inject: [ConfigService],
        useFactory: (configService: ConfigService) => ({
          driver: PostgreSqlDriver,
          dbName: configService.get<string>('DATABASE_NAME'),
          host: configService.get<string>('DATABASE_HOST'),
          port: configService.get<number>('DATABASE_PORT'),
          user: configService.get<string>('DATABASE_USER'),
          password: configService.get<string>('DATABASE_PASS'),
          entitiesTs: ['libs/entities/src/lib'],
          autoLoadEntities: true,
        }),
      }),
    ]
  })
  export class DatabaseModule {}

[B4nan]

You can see that from the stack trace, it is caused by that because nest di is trying to create new instance itself. Remove it and let the nest mikro orm adapter create the instance.

[B4nan]

Having MikroORM explicitly inside providers seems wrong, try removing it.

[SimoneDagna]

Awesome! Removing MikroOrm from providers solved the problem, thanks for the support.

[marcus-sa]

Still seems to be an issue.
Currently when instantiating using forRootAsync, it just causes the app to exit instantly, without any errors thrown at all.

You can find an example here https://github.com/marcus-sa/nest-convoy/blob/feat/mikro-orm/packages/messaging/broker/database/convoy-database.module.ts#L25

[B4nan]

If you want help, provide a simple reproduction and all the details as described in issue template. Your linked project is too huge to review. But this particular issue was always invalid, if you see similar stack trace, it might point to some misusage rather than bug. Make sure you do not have MikroORM inside providers, it will be exported automatically. Also ensure you are calling forRootAsync only once (but that wouldn't probably cause this).

[Saegusae]

I can still reproduce this issue with a similar setup, I dont have anything in providers/exports. Just trying to initialize with forRootAsync will cause the same error even when PostgreSQLDriver is explicitly provided. Worth mentioning this is a NestJS application running under Nx Framework.

Here's the file I'm initializing the root module from, this is called only once by the AppModule entry point:

import { Module } from '@nestjs/common';
import { ConfigModule, ConfigService } from '@nestjs/config';
import { MikroOrmModule } from '@mikro-orm/nestjs';

@Module({
  imports: [
    MikroOrmModule.forRootAsync({
      imports: [ConfigModule],
      inject: [ConfigService],
      useFactory: (configService: ConfigService) => ({
        type: 'postgresql',
        dbName: configService.get<string>('DATABASE_NAME'),
        host: configService.get<string>('DATABASE_HOST'),
        port: configService.get<number>('DATABASE_PORT'),
        user: configService.get<string>('DATABASE_USER'),
        password: configService.get<string>('DATABASE_PASS'),
        entitiesTs: ['libs/entities/src/lib'],
        autoLoadEntities: true,
      }),
    }),
  ]
})
export class DatabaseModule {}

PS. Having the factory method async and return a promise yields the same result.