Accelerate: "Invalid client engine type, please use `library` or `binary`" on Edge about prisma HOT 18 CLOSED

The Prisma code is pretty stable and used by hundreds of thousands of users - so I would suggest you look more into how you use Prisma Client and share that with us in a way we can properly reproduce and understand what you are doing.

from prisma.

from prisma.

@liuhuapiaoyuan Can you try adding engineType = "library" to the generator block in schema.prisma file and check if that resolves the issue?

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider   = "prisma-client-js"
  engineType = "library"
}

from prisma.

same error

from prisma.

I would assume that same thing happens with engineType = "binary" as well, right?

from prisma.

Do you get this error with a hosted database as well? What happens if you don't use a locally running database?

from prisma.

same error

from prisma.

Do you get this error with a hosted database as well? What happens if you don't use a locally running database?

I look at the code unless accelerate is used

from prisma.

Just to confirm, are you invoking npx prisma generate after adding engineType = "library"/"binary" to your schema file?

If not, could you run the prisma generate command and check?

from prisma.

Just to confirm, are you invoking npx prisma generate after adding engineType = "library"/"binary" to your schema file?

If not, could you run the prisma generate command and check?

Of course~~

Every time I make a modification, I have executed npx prisma generate

from prisma.

Thanks for confirming!
Does this happen on a stable version of Next.js as well? It looks like you are using canary version.

from prisma.

yes，i using canary version

but, i think is not Next.js error.

you can watch source code

from prisma.

When exactly do you get this error?
When you try to do a Prisma Client query?

from prisma.

It seems that instantiating the Prisma instance is wrong

from prisma.

This code can reproduce this error. You can try id .
https://github.com/liuhuapiaoyuan/nextjs-prisma-edge-bug

from prisma.

The Prisma code is pretty stable and used by hundreds of thousands of users - so I would suggest you look more into how you use Prisma Client and share that with us in a way we can properly reproduce and understand what you are doing.

I just want to solve the issue of accessing the database in edge within node-postgres. Is there absolutely no way due to the problem with node-postgres?

Additionally, my software actually needs to use sqlite, and I need to use prisma in the middleware of next.js, for example, some logging. My scenario does not allow me to use serverless services.

from prisma.

I just want to solve the issue of accessing the database in edge within node-postgres. Is there absolutely no way due to the problem with node-postgres?

Yes, node-postgres has a bug so it does not work in Next.js or deployed to Vercel, with or withour Prisma - nothing we at Prisma can do about that.

Additionally, my software actually needs to use sqlite, and I need to use prisma in the middleware of next.js, for example, some logging. My scenario does not allow me to use serverless services.

Next.js middleware always runs code in the "edge runtime", there is no way around that: https://nextjs.org/docs/app/building-your-application/routing/middleware#runtime

(Note: All these questions are off topic for this issue about Accelerate again. If you just want to have a discussion instead of report a bug, please open a discussion instead of an issue.)

from prisma.

OK OK , I understand. It's just that there is completely no way。

from prisma.