[Feature Request] Compatibility with Edge Runtime

[ymc9]

Background

Prisma didn't support running in the edge environment (Vercel, CloudFlare, etc.) in older versions, so it wasn't a design goal for ZenStack either. However, things have been changing fast in the past few months:

• The Accelerate cloud offering is fully edge compatible
• The Driver Adapters feature now leverages HTTP protocol to talk to PlanetScale and Neon. It's not edge-compatible yet, but I believe it's not far. We should confirm this with the Prisma team, though.

Proposed Solution

The main obstacle to running ZenStack on the edge today is the environment doesn't allow dynamic require calls. ZenStack uses it to dynamically load generated code (for evaluating access policies) and determine Prisma version (for compatibility with both v4 and v5), and a few other less important occasions.

However, if we go ahead and make the enhance API generated as well, the dynamicity mentioned above can be determined at zenstack generate time instead of runtime. I believe it's doable but requires careful backward compatibility testing and verification in different edge environments.

Question

What are the main edge runtime providers that people care about besides Vercel and CloudFlare?

[ErikDakoda]

I want to note that although I requested this feature, I have since moved away from using Prisma and, therefore, ZenStack in my edge runtime routes altogether. Prisma gets bloated very quickly, with all models included, so it is really easy to exceed the maximum bundle size (Hobby: 1 MB, Pro: 2 MB, Ent: 4 MB).

[ymc9]

I want to note that although I requested this feature, I have since moved away from using Prisma and, therefore, ZenStack in my edge runtime routes altogether. Prisma gets bloated very quickly, with all models included, so it is really easy to exceed the maximum bundle size (Hobby: 1 MB, Pro: 2 MB, Ent: 4 MB).

Got it. May I know what your deployment target is? So it's still bloated even using the Edge version of PrismaClient, right? That's surprising ...

[ErikDakoda]

Yes, @prisma/client/runtime/edge.js and .prisma/client/edge.js are the two largest dependencies, and without them the bundle size goes from 2.84 MB down to 613 KB. I should also be able to remove the third largest dependency, which is zod/lib/types.js.

[ymc9]

Yes, @prisma/client/runtime/edge.js and .prisma/client/edge.js are the two largest dependencies, and without them the bundle size goes from 2.84 MB down to 613 KB. I should also be able to remove the third largest dependency, which is zod/lib/types.js.

OK, that's a surprise. Prisma team should look into it 🤷🏻. What's your alternative now? Drizzle?

[ErikDakoda]

I am saving the data from the client side and I am avoiding database access in the edge function. If I didn't have that option, I would try the new @prisma/adapter-planetscale or access the database through my REST or rRPC API.