Accelerate breaks "PrismaClient is unable to run in this browser environment, or has been bundled for the browser" about prisma HOT 3 CLOSED

@nurul3101 Your understanding is correct. Not only that, but I also tested your hypothesis, and it's right.

I commented out UserPreview in users/[slug].tsx and no error was thrown. I started to debug and noticed that nothing inside that JSX component was the problem.

The problem was that I had import prisma from "@/lib/prisma"; and

export const getPublicUser = async (where: Prisma.userWhereUniqueInput) => {
  const userUnique = prisma.user.findUniqueOrThrow({
  ...

in the same file where the UserPreview component was defined (components/User/Preview/index.tsx)

So I used components/User/Preview/index.tsx only for the JSX and moved getPublicUser to another file, and the error is gone, fixed!

I'm just wondering, why isn't the behavior the same between using Accelerate and not using it? Even though the problem is fixed, should I expect any changes in how Accelerate affects the """bundle""" (I'm unaware of the correct term as I'm ignorant of what's actually happening under the hood) to be able to use my original code, or is this code refactoring expected when using Accelerate?

from prisma.

Hey @walterdiazesa 👋

Thank you for raising this.

If I understand this correctly, Prisma Accelerate works as expected for your one route (pages/works/[slug]/index.tsx) but it doesn't for the other route (pages/users/[slug].tsx) correct?

I see that in your users/[slug].tsx you are importing a component called UserPreview which I assume returns some JSX?
Could you temporarily comment usage of UserPreview in the users/[slug].tsx file and check if you still get the error? My assumption is that the error is caused in components/User/Preview/index.tsx file.

from prisma.

I am glad to hear that the hypothesis was correct. I believe the code refactoring is expected, because UserPreview component - components/User/Preview/index.tsx is rendered on client side and is not server side rendered. The database interactions need to happen on the server side. Previously you were doing database calls in getPublicUser function which was on client side, which caused the error. As soon as you changed the location of the function to be outside the client rendered component, the issue was resolved.

from prisma.