Edge runtime incompatibility error on `$on` or `$use` usage attempt about prisma HOT 4 OPEN

Thanks for the prompt reply and sorry for me being a little sluggish with mine.

I believe I am not calling Prisma from the middleware or any other place that can potentially have the edge runtime turned on. This is my middleware.ts code (pretty much the only place something may break at) - it was configured with accordance to the Edge Compatibility page recommendations from NextAuth docs:

import { authConfig } from '@/config/auth/config'
import { DEFAULT_LOCALE, LOCALES, LOCALE_PREFIX_STRATEGY } from '@/config/intl'
import NextAuth from 'next-auth'
import createI18nMiddleware from 'next-intl/middleware'

const { auth } = NextAuth(authConfig)

const rerouteByLocale = createI18nMiddleware({
  locales: LOCALES,
  defaultLocale: DEFAULT_LOCALE,
  localePrefix: LOCALE_PREFIX_STRATEGY,
})

export const middleware = auth(request => rerouteByLocale(request))

export const config = {
  matcher: ['/((?!api|_next/static|_next/image|favicon.ico).*)'],
}

Therefore, I believe it's actually the second option that is taking place, and I will try to provide a reproduction example ASAP

from prisma.

Getting the same error after trying to call $use instead in this fashion:

const getClient = () => {
  const client = new PrismaClient()
  client.$use(async (params, next) => {
    const before = Date.now()

    const result = await next(params)

    const after = Date.now()

    console.log(
      `Query ${params.model}.${params.action} with ${params.args} took ${after - before}ms`,
    )

    return result
  })
  return client
}

from prisma.

$extends call errors out as well

from prisma.

Where are you trying to use Prisma Client?

Next.js middleware for example is unfortunately always executed in the edge runtime of Vercel, even when running it locally via next dev or similar (see a massive discussion about this here: vercel/next.js#46722), which means you really have to follow these instructions to be able to talk to a database. In that case, this is not related to $on or $use at all and we unfortunately can't do much besides showing the instructions you are seeing.

If you are not trying to use it in middleware or anything similar that runs in the edge runtime, this is a false positive of our detection code. For that case, a reproduction repository with a minimal Next.js app and the absolutely needed code that is needed to trigger this situation would be the best way forward.

from prisma.