"PrismaClient is unable to be run under the Vercel Edge Runtime."

Unanswered

Exzotic posted this in #help-forum

2023-09-05T11:39:51.000Z

Hello! Im getting an issue while trying to use prisma in the middleware.ts file. It works everywhere else just not there for some reason
(Running locally not on vercel)

86 Replies

riský

2023-09-05T11:40:34.000Z

is your page a edge function

ExzoticOP

2023-09-05T11:40:56.000Z

I havent defined either way so

riský

2023-09-05T11:40:56.000Z

like https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes#segment-runtime-option

ExzoticOP

2023-09-05T11:41:02.000Z

It is nodejs

riský

2023-09-05T11:41:18.000Z

so, export const runtime = 'edge' isn't in your code anywere?

ExzoticOP

2023-09-05T11:41:27.000Z

Nowhere

riský

2023-09-05T11:42:11.000Z

hmm, could any libraries be enabeling that for you...

ExzoticOP

2023-09-05T11:42:37.000Z

Not that I could think off

riský

2023-09-05T11:42:38.000Z

but i don't see how that would work

ExzoticOP

2023-09-05T11:42:51.000Z

  "dependencies": {
    "@auth/prisma-adapter": "^1.0.1",
    "@prisma/client": "^5.1.1",
    "@types/node": "20.4.9",
    "@types/react": "18.2.20",
    "@types/react-dom": "18.2.7",
    "autoprefixer": "10.4.14",
    "bcrypt": "^5.1.0",
    "eslint": "8.47.0",
    "eslint-config-next": "13.4.13",
    "next": "13.4.13",
    "next-auth": "^4.23.0",
    "postcss": "8.4.27",
    "prisma": "^5.1.1",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-icons": "^4.10.1",
    "stripe": "^13.1.0",
    "tailwind-merge": "^1.14.0",
    "tailwindcss": "3.3.3",
    "typescript": "5.1.6",
    "zod": "^3.22.1"
  },
  "devDependencies": {
    "@types/bcrypt": "^5.0.0"
  }

riský

2023-09-05T11:42:57.000Z

and submiting a bug report to said url won;t do anything

so, you said some route have this isssue

is it the same ones

ExzoticOP

2023-09-05T11:43:26.000Z

Every page

riský

2023-09-05T11:43:30.000Z

ohh

thats a bit problematic

ExzoticOP

2023-09-05T11:43:50.000Z

I can use prisma fine in the pages / routes, just in the middleware its causing some issues

riský

2023-09-05T11:44:42.000Z

~~i don't remember heading that middlewires force edge runtime... so~~ edit, apparently it does

https://github.com/prisma/prisma/discussions/12602

ExzoticOP

2023-09-05T11:45:23.000Z

I tried adding export const runtime = 'nodejs'; to the middleware.ts but no luck

@riský https://github.com/prisma/prisma/discussions/12602

riský

2023-09-05T11:45:40.000Z

i guess it does... ?

ExzoticOP

2023-09-05T11:49:23.000Z

oh middleware doesnt affect routes either it seems

riský

2023-09-05T11:49:42.000Z

this is a little weird...

ExzoticOP

2023-09-05T11:50:04.000Z

yeah i might just have to add a check in every file that i want to be secure

riský

2023-09-05T11:50:17.000Z

just a quick import of a function

ExzoticOP

2023-09-05T11:50:18.000Z

especially with these admin routes dont want to risk any user being able to access them

riský

2023-09-05T11:51:04.000Z

now i see why nextauth adds this stuff to jwt token, so it doesn't need to use db for middlewire

ExzoticOP

2023-09-05T11:51:46.000Z

yeah i mean i can add the admin field to the token but i dont trust the middelware now

well it just doesnt work on routes is the problem

@Exzotic yeah i mean i can add the admin field to the token but i dont trust the middelware now

riský

2023-09-05T11:52:37.000Z

its good, just as long as all you do is edge server things

sorry for not having a better answer ðŸ˜

ExzoticOP

2023-09-05T11:53:39.000Z

Its all good

Original message was deleted

riský

2023-09-05T11:55:20.000Z

you could probably mark this as solved as it isn't possible so that others may see it on google, but there are so many other results, so it probably doesn't matter

riský

2023-09-05T12:03:12.000Z

as in you use the command, but it doesn't matter

ExzoticOP

2023-09-05T12:08:25.000Z

would you know the best way to apply "middleware" to api routes?

riský

2023-09-05T12:09:36.000Z

sure

is it adding a function that you run?

ExzoticOP

2023-09-05T12:10:18.000Z

yeah i have:

export async function requireAdmin() {
    const session = await getAuthSession();

    if(!session.user || !session.user.admin) return new Response(null, { status: 401 });
}

But im not sure the best way to add it to each admin route

as it also needs to return the actual route function

riský

2023-09-05T12:10:47.000Z

just run requireAdmin at the start of the route

ahh

ExzoticOP

2023-09-05T12:10:59.000Z

yeah but it will continue the rest

riský

2023-09-05T12:11:03.000Z

what i would do is create a wrapper

that takes in a function and either returns that function or that error

Asian black bear

2023-09-05T12:11:46.000Z

I didn't read through the entire thread, but the middleware is running on Edge and you can't change it. And Prisma is not supported on Edge at all.

riský

2023-09-05T12:12:10.000Z

they are basicly deciding to add the checks to all the api routes now... as of that reason

ExzoticOP

2023-09-05T12:12:28.000Z

yeah as middleware doesnt even touch routes for some reason

I think in the future I might just have to go back to express + react, its nice having it in one but it seems to have a lot of problems for me at least

riský

2023-09-05T12:15:05.000Z

i would do this

function requireAdmin(fn: Function): Function {
  return async (...args: any[]) => {
    const session = await getAuthSession();

    if (!session.user || !session.user.admin) {
      return new Response(null, { status: 401 });
    }

    return await fn(...args);
  };
}

and use it like

export const const GET = requireAdmin(() => {
  // This function can only be called by admins.
})();

(i think this should work)

ExzoticOP

2023-09-05T12:15:37.000Z

ah thanks, will try it

riský

2023-09-05T12:15:53.000Z

but you may need to fix the types as i didn't emember what they were

(as any would be a bit annoying)

Peterbald

2023-09-05T12:41:00.000Z

@Exzotic Are you getting Vercel Edge Runtime error?
It is because you called PrismaClient in middleware.ts

riský

2023-09-05T12:41:41.000Z

yeah, thats the error and as near said: https://ptb.discord.com/channels/752553802359505017/1148583270280339567/1148591301533638738

Peterbald

2023-09-05T12:42:10.000Z

Like this

To avoid that error you have to use @prisma/clent/edge to config Prisma

riský

2023-09-05T12:42:48.000Z

but does that require their service thing?

Peterbald

2023-09-05T12:42:49.000Z

// import { PrismaClient } from '@prisma/client';
import { PrismaClient } from '@prisma/client/edge'
import { withAccelerate } from '@prisma/extension-accelerate';

const globalForPrisma = global as unknown as { prisma: PrismaClient };

// { log: ["query"] }; // Previously housed within PrismaClient();
export const prisma = globalForPrisma.prisma || new PrismaClient().$extends(withAccelerate());

if (process.env.NODE_ENV != "production") globalForPrisma.prisma;

ExzoticOP

2023-09-05T12:43:03.000Z

ah well my main concern was api routes and for some reason middleware doesnt affect them

riský

2023-09-05T12:43:04.000Z

use 3 back ticks

Peterbald

2023-09-05T12:43:51.000Z

And have to use another DATABASE_URL.
prisma://accelerate.prisma-data.net/?api_key=......

riský

2023-09-05T12:44:31.000Z

yeah, not a native solution - while good suggestion, it requires signing up to another thing - but they may be willing