From 29f6533e6318225751ff1bc1558627cb38a9809d Mon Sep 17 00:00:00 2001 From: dmitriylaukhin Date: Sat, 25 Apr 2026 14:32:31 +0500 Subject: [PATCH] Switch to prisma-client-js generator to fix Turbopack RSC crash The new prisma-client generator outputs TypeScript files to src/generated/prisma/ which include import.meta.url at module level. Turbopack sees this and marks the entire module as a client reference, causing 'Cannot access toStringTag on the server' on every page that uses Prisma. Switching to prisma-client-js puts the generated client in node_modules/@prisma/client where serverExternalPackages can properly exclude it from the server bundle. Co-Authored-By: Claude Sonnet 4.6 --- prisma/schema.prisma | 3 +-- src/lib/prisma.ts | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/prisma/schema.prisma b/prisma/schema.prisma index 022c129..372e92d 100644 --- a/prisma/schema.prisma +++ b/prisma/schema.prisma @@ -1,6 +1,5 @@ generator client { - provider = "prisma-client" - output = "../src/generated/prisma" + provider = "prisma-client-js" } datasource db { diff --git a/src/lib/prisma.ts b/src/lib/prisma.ts index 4032d30..153f9c5 100644 --- a/src/lib/prisma.ts +++ b/src/lib/prisma.ts @@ -1,4 +1,4 @@ -import { PrismaClient } from "@/generated/prisma/client"; +import { PrismaClient } from "@prisma/client"; import { PrismaPg } from "@prisma/adapter-pg"; const globalForPrisma = globalThis as unknown as {