Entity types cannot be resolved in PNPM monorepo

[gurvancampion]

I'm having trouble running nexus-prisma in PNPM monorepo. I have two packages users & posts, when I run the command prisma run generate, nexus-prisma get resolved at the root directory instead of the package directory. Which causes entity types cannot be resolved as they got overwritten.

What should be expected is the generated output should be at the package node_modules level instead of the root directory, like @prisma/client in the screenshot below.

Screenshot

It's a similar issue to this one for Prisma: prisma/prisma#7484

[jasonkuhrt]

Resolution is currently relative to where nexus-prisma is installed on disk.

What algorithm do you suggest to solve this?

I do not know how pnpm works.

[millsp]

Yes, that's right. Because we resolve the client relatively to where the prisma is installed, we end up using the hoisted node_modules at the root of your project (your workspace). Here's an example project to shows how to do this with pnpm:
https://github.com/prisma/e2e-tests/tree/dev/packagers/pnpm-workspaces-custom-output

Notice here that the import is not @prisma/client any longer but .prisma/client.

And a more detailed explanation of this, follow here prisma/prisma#6603 (comment)

Let me know if it helped.

[jasonkuhrt]

@millsp Are you saying the way nexus-prisma imports @prisma/client needs to change?

[jasonkuhrt]

@millsp in that example the output has been customized https://github.com/prisma/e2e-tests/blob/dev/packagers/pnpm-workspaces-custom-output/workspace/sub-project-2/prisma/schema.prisma#L3.

NP would use that as the import specifier.

So I see nothing new that NP needs to do.

[millsp]

Yep, custom output is the way to make it work with hoisted node_modules. Just need for @gurvan-guss to confirm if that worked.

[gurvancampion]

Yes I confirm it worked by specifying a custom output :)