Execute Prisma commands from the project dir

[sodic]

Reported in version: 0.15.2

---

We execute Prisma commands from the generated server dir (.wasp/out/server). We do this to ensure Prisma correctly picks up our env vars: #1662.

Running Prisma from the server dir causes unexpected behavior (often because different stuff gets installed in different node_modules folders).

We should solve the env variable issue and find a way run all commands from the project's root directory.

Important

The command for generating the Prisma client is also run from .wasp/out/server, but the client is generated in the correct location (top-level node_modules). I guess this is because our SDK (wasp package) lists it as a dependency.

If that's true, it's very implicit and flaky, and we should fix that too.

[infomiho]

I'd love it if we could go full vanilla with Prisma.

The biggest blocker is our injected auth models. If we could maybe find a way to inject it via some Prisma plugin / generator thing - that would make it work for us. And then, Wasp just runs Prisma commands with much intervention, everything lives in the user-land and everyone is happier.

I know this is maybe out of scope for this issue, but I wanted to voice this somewhere :)

[Martinsos]

Hm yeah, more vanilla we go, the less we interfere and possibly stop people from using some features. But, we also should think a bit upfront about Full Stack Modules -> they might again need us to have more control over Prisma schema hm.

[sodic]

I met @jkomyno at Armada JS and, if I understood him correctly, the next version of Prisma will no longer require relations to have a relation field on each model.

@infomiho Does that help with injected auth models?

@jkomyno Feel free to correct me if I misunderstood something :)