Can't use Prisma client in Next.js middleware, even when deploying to Node.js #21310
Description
Bug description
Next.js middleware seems to fail the edge runtime check, even when deployed to Node.js:
Error: PrismaClient is unable to run in Vercel Edge Functions. As an alternative, try Accelerate: https://pris.ly/d/accelerate.
If this is unexpected, please open an issue: https://github.com/prisma/prisma/issues
Wasn't sure if this is a Next or a Prisma bug.
How to reproduce
- Clone https://github.com/markspolakovs/next-prisma-repro
- Run
yarn dev - Visit http://localhost:3000
Expected behavior
DB operations to work inside middleware.
Prisma information
generator client {
provider = "prisma-client-js"
}
datasource db {
provider = "sqlite"
url = env("DATABASE_URL")
}
model User {
id Int @id @default(autoincrement())
}import { PrismaClient } from "@prisma/client";
import { NextRequest, NextResponse } from "next/server";
const prisma = new PrismaClient();
export async function middleware(req: NextRequest): Promise<NextResponse> {
const user = await prisma.user.findFirst();
return NextResponse.next();
}Environment & setup
- OS: macOS arm64
- Database: SQLite
- Node.js version: v18.17.0
Prisma Version
prisma : 5.3.1
@prisma/client : 5.3.1
Current platform : darwin-arm64
Query Engine (Node-API) : libquery-engine 61e140623197a131c2a6189271ffee05a7aa9a59 (at node_modules/@prisma/engines/libquery_engine-darwin-arm64.dylib.node)
Schema Engine : schema-engine-cli 61e140623197a131c2a6189271ffee05a7aa9a59 (at node_modules/@prisma/engines/schema-engine-darwin-arm64)
Schema Wasm : @prisma/prisma-schema-wasm 5.3.1-2.61e140623197a131c2a6189271ffee05a7aa9a59
Default Engines Hash : 61e140623197a131c2a6189271ffee05a7aa9a59
Studio : 0.494.0