Skip to content

How to fix the `Already 10 Prisma Clients are actively running` error

New Course Coming Soon:

Get Really Good at Git

I was using Prisma in my Next.js app and I was doing it wrong.

I was initializing a new PrismaClient object in every page:

import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()

After some point, during app usage, I received the error Already 10 Prisma Clients are actively running and also a Address already in use.

To fix this, I exported this Prisma initialization to a separate file, lib/prisma.js:

import { PrismaClient } from '@prisma/client'

let prisma

if (process.env.NODE_ENV === 'production') {
  prisma = new PrismaClient()
} else {
  if (!global.prisma) {
    global.prisma = new PrismaClient()
  prisma = global.prisma

export default prisma

The production check is done because in development, npm run dev clears the Node.js cache at runtime, and this causes a new PrismaClient initialization each time due to hot reloading, so we’d not solve the problem.

I took this code from

Finally I imported the exported prisma object in my pages:

import prisma from 'lib/prisma'
Are you intimidated by Git? Can’t figure out merge vs rebase? Are you afraid of screwing up something any time you have to do something in Git? Do you rely on ChatGPT or random people’s answer on StackOverflow to fix your problems? Your coworkers are tired of explaining Git to you all the time? Git is something we all need to use, but few of us really master it. I created this course to improve your Git (and GitHub) knowledge at a radical level. A course that helps you feel less frustrated with Git. Launching May 21, 2024. Join the waiting list!

Here is how can I help you: