graphql-nexus/nexus-prisma

Yarn PNP Compatibility

SagnikPradhan opened this issue · 4 comments

Screenshot

image

Description

Prisma seemed to be stuck on generate command, running it with DEBUG="*" showed it had to do with floggy not mentioning chalk as a (peer, I assume) dependency.

Repro Steps/Link

I presume any project using yarn 2+ instead of npm and running yarn pnpify prisma generate

Edit - Do this instead #191 (comment)

Temporary solution would be using node_modules linker instead with yarn config use nodeLinker node-modules (followed by yarn install OFC)

Workaround if you are hitting this with pnpm: prisma/prisma#10291 (comment)

Aaah, right, forgot about this issue. You could do similar with yarn pnp too, using package extensions and declaring chalk (4.x) as a dependency of floggy.

I resolved this problem.

I just added chalk: ^4.1.2 to floggy dependency in yarn.lock