size-limit report 📦

Would it be possible to have a toggle to always opt in in using wasm?module? If I understand things correctly, then this would be desired for every nuxt project - independent on where it would be published in the end.

Would it be possible to have a toggle to always opt in in using wasm?module? If I understand things correctly, then this would be desired for every nuxt project - independent on where it would be published in the end.

Hi @tobiasdiez, we have previously discussed this possibility with the maintainer of unjs/unwasm, but it shouldn't be necessary at this moment.

Currently, and in the upcoming Prisma 6.15.0 release as well, the Query Compiler Wasm will be loaded as following:

• from a base64-encoded file, if you specified runtime = "nodejs" | "deno" | "bun" (if you didn't specify anything, nodejs is the default)
• from a local ./<filename>.wasm?module import, if you specified runtime = "workerd" | "vercel-edge"

So, if your Nuxt project is hosted on e.g. Vercel's Node.js runtime or Deno Deploy, Prisma will load the base64-encoded file.
I hope this helps :)

Sounds good. I'm happy with whatever solution as long as I can successfully create a production deployment against the nodejs runtime with nuxt + prisma 🦊 Currently, this is not working with the base64-encoded file.

Sounds good. I'm happy with whatever solution as long as I can successfully create a production deployment against the nodejs runtime with nuxt + prisma 🦊 Currently, this is not working with the base64-encoded file.

Can you link me to a project that doesn't work in the scenario you describe? I have this example (a copy of https://github.com/prisma/prisma-examples/tree/feat/prisma-client-fixes/generator-prisma-client/nuxt3-starter-nodejs) that works well both locally and deployed to Vercel.

(Maybe you shared a link in another thread already; if so, I apologise. My Github notifications are exploding lol)

I've played around with the examples in the prisma-example repo and none of them are working for me at the moment. I've opened PR's and issues in that repo. I'm aware that they use slightly older prisma versions, but I actually run in the same issues with the latest release. Would be nice if you could have a look.

• Nuxt: Run build during CI tests prisma-examples#8279
• Nuxt, generator-prisma-client: Use experimental wasm mode of nitro prisma-examples#8281
• Nuxt, generator-prisma-client: Invalid prisma.quotes.findMany() invocation in production build prisma-examples#8280 (this is actually the same as what I'm getting at chore: use new Prisma ESM generator and improve client imports JabRef/JabRefOnline#2647 when trying to publish to azure)

(and a few smaller fixes in prisma/prisma-examples#8282 should be ready to go)

I've played around with the examples in the prisma-example repo and none of them are working for me at the moment. I've opened PR's and issues in that repo. I'm aware that they use slightly older prisma versions, but I actually run in the same issues with the latest release. Would be nice if you could have a look.

• Nuxt: Run build during CI tests prisma-examples#8279
• Nuxt, generator-prisma-client: Use experimental wasm mode of nitro prisma-examples#8281
• Nuxt, generator-prisma-client: Invalid prisma.quotes.findMany() invocation in production build prisma-examples#8280 (this is actually the same as what I'm getting at chore: use new Prisma ESM generator and improve client imports JabRef/JabRefOnline#2647 when trying to publish to azure)

(and a few smaller fixes in prisma/prisma-examples#8282 should be ready to go)

Have you used the examples from the feat/prisma-client-fixes branch (the one I posted) as a reference? Or do they also not work for you?

That was with latest branch, but same error with your branch (see prisma/prisma-examples#8260 (comment)).

That was with latest branch, but same error with your branch (see prisma/prisma-examples#8260 (comment)).

Replied in prisma/prisma-examples#8260 (comment). Not a Prisma error :)