Dependency resolution fails with `@mikro-orm/cli` and `pnpm`

Describe the bug NestJS is unable to resolve SqlEntityManager in a pnpm monorepo only when @mikro-orm/cli is installed.

Stack trace

ERROR [ExceptionHandler] Nest can't resolve dependencies of the AppService (?). Please make sure that the argument SqlEntityManager at index [0] is available in the AppModule context.

Reproduction (duckies/mikro-orm-cli-issue) I created a minimal reproduction that should fail on pnpm i && pnpm dev, but will work once @mikro-orm/cli is removed from the ./packages/server/package.json’s dependencies and commands reran. I also included a yarn@v1 branch and NestJS is working with all dependencies installed.

Additional context I’m unsure if this is an issue with mikro-orm, pnpm, or otherwise. I know pnpm often duplicates, and thus breaks, @nestjs/core, but I don’t think this is the case here.

Versions

Dependency	Version
node	16.13.1
typescript	4.7.4
mikro-orm	5.3.1
your-driver	postgresql

[B4nan]

It would be indeed good to support pnpm but I am having hard times to even debug this, when going thru the symlinks it looks good to me 🤷 But pnpm why kinda confirms there are two installs.

I was thinking how to get around this, but it all seems semi breaking, so would rather keep that for v6. But we could have the CLI package with only peer deps and change how we import things in that package to not fall apart in case the deps are not there (we just need nice error handling, no special functionality). The mikro-orm metapackage could work the same as e.g. jest CLI - it would depend on the @mikro-orm/cli and prefer its locally installed version (there is an npm package for this).

[bartvanremortele]

@B4nan I can confirm that importing from the knex package and injecting SqlEntityManager works. In our case the @mikro-orm/knex dependency was not explicitly installed but I still had this exact same issue. It was being pulled in as a dependency of @mikro-orm/postgresql