Prisma 6.7.0: All models in schema "can't be defined" because they "already exist"

[opaque moth]

You selected the carefully hand-crafted route. A dev artisan will respond soon. Meanwhile, the #ask-ai channel awaits if you're curious!

[tame shore]

Hey!

Did the issue started occurring after upgrading to Prisma 6.7.0?
Can you please provide a reproduction so that we can investigate?

[worldly sand]

Sorry the late response! I tried to delete this thread but the best I was able to do was delete the first chat.

I figured out what the issue was, and said something about it in #💬│chat . Basically I was outputting the Prisma client into /prisma/client, and the schema file that gets generated within the client was apparently getting treated as an extra schema file in addition to the one I created. Hence, since it was an identical copy, every model declaration had an error for being a duplicate.

My solution was switching to generating the client into /prisma-client, and leaving /prisma to only include my schema.prisma.

[bitter trench]

@worldly sand are you saying that if you generate to a folder that is not a child of Prisma then this is not an issue anymore? I didn't try that because I had assumed that vs code would still detect both schemas and complain.