npx prisma generate --no-engine, breaking nextjs build
HI guys. Just started with accelerate + postgres. Reading the documentation we should be using npx prisma generate --no-engine to minize package size. However during the ci build (nextjs) after generate. We are seeing a error saying:
wonder how we can get around it?
Thank you.
6 Replies
You selected the carefully hand-crafted route. A dev artisan will respond soon. Meanwhile, the
#ask-ai channel awaits if you're curious!also found out today. if I use the no-engine option to generate the client. I cannot use normal postgres url. This present a problme in testing where is just a normal docker postgres.
Yes, if you need normal postgres url, then it will still require the engines. Though, this will change with Prisma 7.
Do you get the same error if you don't use the
--no-engine flag?Thank you for the reply.
Yes in my CI when building nextjs. That error comes when i generate w/ --no-engine. the test discovery is a 2nd problem
I meant do you get the same error even if you don't pass the
--no-engine flag in the CI?sorry..
if we dont use --no-engine we DO NOT get the error
HI @Nurul did i loose you?