PNP & MikroOrm + NestJS

[lmnogues]

Describe the bug

In a repo configured to use yarn pnp, there is some issue on the configuration used by mikroOrm to start

I've put the following repo to demo the issue
https://github.com/lmnogues/mikro-orm_nestjs_pnp_issue

In the file mikro-orm.config.ts i've not setup the configUrl because I want it to be provided by the configuration module.
The migration will run, but the project will not start.

If we reset yarn to use "node-modules" by changing the .yarnrc.yaml and re-install/build & run the project it will run properly.

Reproduction

yarn install
yarn build
yarn dev

What driver are you using?

@mikro-orm/postgresql

MikroORM version

6.4.1

Node.js version

node 22.12.0 / typescript 5.7.2

Operating system

all

Validations

• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord.
• The provided reproduction is a minimal reproducible example of the bug.

[B4nan]

If you think it's about the ORM itself and not the Nest adapter, please provide a repro without nest involved, but my guess is its about it, so moving the issue to this repo.

I can imagine its caused by the tryRequire we do, which fails with the useFactory that has required params. See #184 for proposed solution, maybe you could verify locally if its about this.

[lmnogues]

Sorry for the missplaced issue :)
I'll try the #184 workaround and get back quiclky.

[lmnogues]

The #184 workaround seems to be working, but it's very unintuitive. At lease it should be documented somewhere in the docs and not in an "Unanswered" issue