A big 2M wasm file created after implementing prisma
I'm using NextJS combining with (Prisma + D1 Adapter), I don't know why Prisma produced such a large wasm file resulting in a build failure in Cloudflare pages.

Solution:Jump to solution
That’s correct, yes. The file is our query engine. You can learn more about that here: https://www.prisma.io/docs/orm/more/under-the-hood/engines
Engines | Prisma Documentation
Prisma's query engine manages the communication with the database when using Prisma Client. Learn how it works on this page.
3 Replies
After using bundle analyzer, I can conclude that this wasm is Prisma

Solution
That’s correct, yes. The file is our query engine. You can learn more about that here: https://www.prisma.io/docs/orm/more/under-the-hood/engines
Engines | Prisma Documentation
Prisma's query engine manages the communication with the database when using Prisma Client. Learn how it works on this page.