Turborepo + Prisma + TRPC
quick sanity check before I drop the idea of letting turborepo cache prisma
has anyone run into this error when using prisma + a custom generated output with next-auth or trpc?
https://github.com/prisma/prisma/issues/13233
I'm using
yarnGitHub
Error with custom output in NPM monorepo: `Error: ENOENT: no such f...
Bug description When attempting to use a Prisma client with a custom output in an NPM monorepo, I get the following error: Error: ENOENT: no such file or directory, open 'schema.prisma&...
3 Replies
Whenever I generate to
node_modules directly and interact with prisma I don't run into this issue at allyou can check https://github.com/t3-oss/create-t3-turbo
GitHub
GitHub - t3-oss/create-t3-turbo: Clean and simple starter repo usin...
Clean and simple starter repo using the T3 Stack along with Expo React Native - GitHub - t3-oss/create-t3-turbo: Clean and simple starter repo using the T3 Stack along with Expo React Native
Ah I see thanks
It looks like Theo had already resolved this. Wasn’t sure if this was the same issue since I remember he was using pnpm