Hi @JoshuaPuello 👋

Thank you for raising this question.

Can you please try generating the types in the default location (of node_modules) by removing this output from the schema file

output   = "../dist/generated/client"

and export it like

export { PrismaClient } from '@prisma/client'

If this answers your question, it would be great if you could mark this Discussion as answered to indicate that it has been resolved.

Otherwise please let us know how else we can help you further or close the Discussion if it was resolved in some other way 🙏

This should not be happening. Once a Client is created, it should stay where it is. What version of Yarn and what command exactly are you using? Is this reproducible when you create a new project?

You could just use a simple copy command npx prisma generate && cp -r node_modules/.prisma otherProjectPath/node_modules/.prisma

If you add it as a package json scripts you could call it with something like npm run generate or yarn generate

Hey Yassin 👋 this is a great initiative and I'd love to see such a guide that makes it easier for the community to build their own generators!!

However, there's a major caveat to this. The DMMF is an undocumented API that's not considered part of the official API surface and might break unexpectedly with any release, so it's very intentionally not documented in our own resources (somewhat related context also in this issue: #10725).

I would still love to see such a guide, do you maybe have a personal blog where you could publish it? Otherwise, platforms like Hashnode or dev.to are great to publish blog posts without the need of setting up your own blog. While we are not able to include such a guide in our own resources, I do think we can link to it from the Community generators-section in our docs!

Update for June 2024

See original solution below.
There are two options today that would work without disabling Yarn Plug'n'Play.

1. Custom Prisma Output Directory
   Prisma allows configuration of where it places the files of the generated client. To do so, set the output property in the generator block. It is best to also set the same path in your .gitignore.

generator client {
  provider = "prisma-client-js"
  output   = "../src/generated/client"
}

Full Docs: https://www.prisma.io/docs/orm/prisma-client/setup-and-configuration/generating-prisma-client#using-a-custom-output-path

2. Yarn PnPify
   This acts as a middleman to redirect Prisma's output. See the comment from Moses Gamelli below for instructions.

After having tested a number of different things, I believe I have found a solution.

The Problem

The problem lies in how Yarn is resolving imports. Prisma CLI generates the client (by default) to node_modules/.prisma. Even when nodeLinker is set to node-modules, Yarn tries to resolve this import to .yarn/unplugged/<folder-name>, where the generated client does not exist.

The Solution

In order to fix this resolution problem, we have to create a custom resolution for the .prisma folder. This assumes that you do not have a custom output path.

# .yarnrc.yml

nodeLinker: node-modules

packageExtensions:
  "@prisma/client@*":
    dependencies:
      ".prisma": 'link:See "resolution" field of package.json'

# package.json

{
  ...
  "resolutions": {
     ".prisma": "link:node-modules/.prisma"
  }
}

Credit to this user on Github

That's what I did in package.json file (It was a deploy a Next app on Versel) I just added generate command to the build script:

"scripts": {
    "dev": "next dev",
    "build": "prisma generate && next build",
    "start": "next start",
    "lint": "next lint"
  },

Not sure if it is a correct way, though..