# Fix 'PrismaClient is unable to be run in the browser' in Next.js

> Fix the Next.js error PrismaClient is unable to be run in the browser by keeping Prisma code and its import inside getStaticProps on a page route only.

Author: [Flavio Copes](https://flaviocopes.com/about/) | Published: 2021-05-14 | Updated: 2021-07-08 | Topics: [Next.js](https://flaviocopes.com/tags/next/) | Canonical: https://flaviocopes.com/nextjs-fix-already-10-prisma-clients/

I ran into this error while working on a [Next.js](https://flaviocopes.com/nextjs/) website:

`PrismaClient is unable to be run in the browser` 

I had this page and it all worked fine until I commented one line in my code, in particular in my `getStaticProps()` method.

In that line I called a method from my [Prisma](https://flaviocopes.com/prisma/) instance, which I imported at the top of the page file.

Basically Next.js will see which code we use in `getStaticProps()` and will use it for the backend. It will not ship it to the frontend.

When I commented out the line in `getStaticProps()` where I used Prisma, Next.js included Prisma in my frontend code, and I got that error `PrismaClient is unable to be run in the browser`

The solution was to also comment (or remove) the Prisma import.

Also remember that `getStaticProps()` is only called on page routes, not in other components, so if this error comes from a component, you have to move the logic up to the page route component.