Nest cannot export a provider/module that is not a part of the currently processed module (MikroOrmCoreModule). Please verify whether the exported MongoMikroORM is available in this particular context.

[snigdha920]

Describe the bug
A clear and concise description of what the bug is.

When starting my nestjs application that uses both postgres and mongodb depending on the configuration provided, I see this error since v6.0.0:

Nest cannot export a provider/module that is not a part of the currently processed module (MikroOrmCoreModule). Please verify whether the exported MongoMikroORM is available in this particular context.

Stack trace

[Nest] 12276  - 05/21/2024, 2:26:56 PM     LOG [NestFactory] Starting Nest application...
[Nest] 12276  - 05/21/2024, 2:26:56 PM   ERROR [ExceptionHandler] Nest cannot export a provider/module that is not a part of the currently processed module (MikroOrmCoreModule). Please verify whether the exported MongoMikroORM is available in this particular context.

Possible Solutions:
- Is MongoMikroORM part of the relevant providers/imports within MikroOrmCoreModule?

Error: Nest cannot export a provider/module that is not a part of the currently processed module (MikroOrmCoreModule). Please verify whether the exported MongoMikroORM is available in this particular context.

Possible Solutions:
- Is MongoMikroORM part of the relevant providers/imports within MikroOrmCoreModule?

    at Module.validateExportedProvider (/Users/snigdhasingh/Development/nestjs-example-app/node_modules/@nestjs/core/injector/module.js:308:19)
    at addExportedUnit (/Users/snigdhasingh/Development/nestjs-example-app/node_modules/@nestjs/core/injector/module.js:276:67)
    at Module.addExportedProvider (/Users/snigdhasingh/Development/nestjs-example-app/node_modules/@nestjs/core/injector/module.js:287:9)
    at NestContainer.addExportedProvider (/Users/snigdhasingh/Development/nestjs-example-app/node_modules/@nestjs/core/injector/container.js:168:19)
    at DependenciesScanner.insertExportedProvider (/Users/snigdhasingh/Development/nestjs-example-app/node_modules/@nestjs/core/scanner.js:291:24)
    at /Users/snigdhasingh/Development/nestjs-example-app/node_modules/@nestjs/core/scanner.js:148:50
    at Array.forEach (<anonymous>)
    at DependenciesScanner.reflectExports (/Users/snigdhasingh/Development/nestjs-example-app/node_modules/@nestjs/core/scanner.js:148:17)
    at DependenciesScanner.scanModulesForDependencies (/Users/snigdhasingh/Development/nestjs-example-app/node_modules/@nestjs/core/scanner.js:101:18)
    at async DependenciesScanner.scan (/Users/snigdhasingh/Development/nestjs-example-app/node_modules/@nestjs/core/scanner.js:31:9)

To Reproduce
Reproduction repo: https://github.com/snigdha920/nestjs-example-app

Expected behavior
A clear and concise description of what you expected to happen.

The app should start, like it did with v5.2.3

Versions
All the versions can be found in the reproduction repo.

[B4nan]

I would guess this is because you import the MikroORM class from mongo package but only register the postgres driver - you cant do that, if you want to support both mongo and postgres, you should only import it from the core package. MongoMikroORM will be registered only if you init the mongo driver.

[B4nan]

Hmm but I dont see any place where you would be doing that... :] Let me have a closer look.

[B4nan]

Ok, I see what's happening, its caused by the fallback to mongo driver and a wrong resolution of the options because of useFactory.

[snigdha920]

Yes indd, we only import MongoDriver from the @mikro-orm/mongodb in the reproduction.

[B4nan]

Ok, this is really weird, but the actual problem is that when executing your useFactory method, the path import fails to resolve. This fixes your repro:

-import path from 'path';
+import { join } from 'path';

(and use the join method instead of path.join)

[B4nan]

Changed the commit message to match what its doing, so the final commit is here: 7e73205

[snigdha920]

Thx, I'll try it out! Should we export the Mikro providers of all the installed packages if the driver is not inferred? Because if the driver is unknown, then any of the installed packages could be in use.

[B4nan]

I really dislike that there are the driver names hardcoded here, it's just a workaround, in the long run I want to remove all of that and always use the config, but for that I think we still need to improve the support for useFactory since we don't inject any dependencies into it and it might expect some.

My fix only registers the missing provider which is tried to be exported, that was the bug.

[snigdha920]

I see, cool. I'll try it once you publish a new release and let you know. If I install the package from github like:

"@mikro-orm/nestjs": "git://github.com/mikro-orm/nestjs.git#7e73205567b10cdd4963d420569815268ad326ba",

I get a module "@mikro-orm/nestjs" not found everywhere it's used. I can update the import to "@mikro-orm/nestjs/src" and my IDE stops complaining, but the built image still doesn't find the package, so I'll just wait for the new release. :]

[B4nan]

You could just patch the package manually, its only a single line change.