alphabet yellow question NextJS app in monorepo is unable t Prisma #orm-help

:alphabet-yellow-question: *NextJS app in monorepo...

Richard

04/18/2022, 2:48 PM

alphabet yellow question NextJS app in monorepo is unable to locate
schema.prisma
(generated in a separate package in the same monorepo) Question What is the best way for me to setup the monorepo? Problem When I import prisma from the package in my

web

app, prisma is unable to locate the

schema.prisma

file:

Copy code

error - Error: ENOENT: no such file or directory, open '/Users/xxx/rootDir/apps/web/.next/server/pages/api/trpc/schema.prisma'

This may be related to the following prisma issues: • https://github.com/prisma/prisma/issues/9435#issuecomment-1065879963 • https://github.com/prisma/prisma/issues/10512 (supposed to be fixed via #12427) Context • I have a monorepo setup with an

apps/web

nextJS app and a separate

packages/database

package with prisma inside. • The database package builds via tsup to

packages/database/dist

Copy code

apps/
├─ web/                          # <-- nextJS app (unable to detect schema)
packages/
├─ database/
│  ├─ prisma/                    # prisma setup
│  │  ├─ schema.prisma
│  ├─ src/
│  │  ├─ client.ts               # exports PrismaClient & global.prisma type in prod
│  │  ├─ index.ts                # exports from prisma client
│  │  ├─ seed.ts                 # prisma seeding script for local dev
│  ├─ .env.example               # `DATABASE_URL` env var
│  ├─ tsup.config.js             # builds to /dist folder in this package

Hwanseok Yu

04/19/2022, 11:04 AM

Did you solve this problem? I have same issue

Richard

04/19/2022, 11:50 AM

No, not yet! :( I've seen quite a few people having issues with Prisma in a monorepo.

Nurul

04/19/2022, 1:31 PM

Hey Richard 👋 Is this Issue still persisting for you once you upgrade to the latest dev prisma version available as

@prisma/client@dev

Referring to this comment

Richard

04/30/2022, 6:46 PM

Hi @Nurul, so I spent most of the day today to resolve this and it finally worked. I had updated prisma earlier and the issue was present. I didn’t update it today but was able to resolve the issue. To be honest, I’m not 100% certain what the problem was but mainly played around with package.json’s & turbo.json after I saw in some log that the prisma-client configuration was set up properly.

🙌 1

Richard

04/30/2022, 6:46 PM

Thanks for following up though, really appreciate it. 🙏

🙌 1

manuel

07/07/2022, 8:56 AM

@Richard I am trying to do the same, do you maybe have a sample repo? 😄

Richard

07/12/2022, 11:46 PM

@manuel I do not unfortunately. But if you have a repo, I can try and take a look. (sorry for the embarrassingly delay in responding)

7 Views

Open in Slack

Previous Next