fix: update prisma to 7.0.0 and use prisma-client generator

[ph1losof]

Description

This PR fixes the “Prisma Client could not locate the Query Engine (rhel-openssl-3.0.x)” error by moving the project to Prisma 7, which introduces a new runtime and generator designed for Next.js App Router and Turbopack.

With the new generator, Prisma bundles engine binaries in a stable, traceable structure that Vercel reliably includes during deployment. The added prisma.config.ts centralizes Prisma settings, ensures consistent schema resolution, and improves monorepo compatibility. Updating the generator output to ../generated places the client in the source tree, making file tracing deterministic.

Together, these updates ensure the correct query engine is always included, resolving the runtime error and making Prisma fully compatible with Next.js + Vercel in a monorepo setup.

Related Issues

Closes #646

Checklist

• My code follows the code style of this project.
• I have performed a self-review of my code.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation, if necessary.
• I have added tests that prove my fix is effective or my feature works.
• New and existing tests pass locally with my changes.

Screenshots (if applicable)

Additional Notes

Prisma now officially recommends using the prisma-client generator introduced in Prisma 7. This generator replaces the older prisma-client-js generator and is the preferred, future-proof way to generate Prisma Client in all new projects.

[vercel]

@ph1losof is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​prisma/​client-runtime-utils@​7.0.0

View full report