[WIP] Update Prisma generator to include rhel-openssl-3.0.x

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

Problem

Prisma Client fails at runtime with: "Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x"." This happens in deployed environments (for example Vercel) where the required Prisma query engine binary isn’t present in node_modules/.prisma/client. The repository already runs prisma generate in postinstall and build, but the Prisma generator configuration doesn't include the rhel-openssl-3.0.x binary target, so the platform-specific engine isn’t downloaded during generate.

Goal

Ensure Prisma generates and includes the correct Query Engine for rhel-openssl-3.0.x so that deployments do not fail with the "engine not found" error.

What to change

1. Modify prisma/schema.prisma generator block to explicitly request the rhel-openssl-3.0.x binary target (and keep native). The change will look like:

generator client {
provider = "prisma-client-js"
engineType = "binary"
binaryTargets = ["native", "rhel-openssl-3.0.x"]
}

Rationale: adding binaryTargets instructs Prisma to download the query engine binary for the specified platforms during prisma generate, ensuring the correct libquery_engine-*.so.node is placed under node_modules/.prisma/client.

2. Keep package.json postinstall script (already present) so engines are generated on install in CI/CD or Vercel. No change needed to package.json, but call out that deployments that use pnpm or other package managers must run prisma generate on install or use a build hook that runs it.

Testing steps (what the agent will do in the PR):

• Update prisma/schema.prisma as above.
• Run npx prisma generate locally to confirm the new binary target is fetched (can't run in PR, but will include changes only).
• Open a short PR with the change and a small note in the commit message.

Files to change

• prisma/schema.prisma: update generator client block to include engineType and binaryTargets.

Please create a pull request that makes this change in the repository Srijan76-code/vyne-ai.

This pull request was created as a result of the following prompt from Copilot chat.

Problem

Prisma Client fails at runtime with: "Prisma Client could not locate the Query Engine for runtime "rhel-openssl-3.0.x"." This happens in deployed environments (for example Vercel) where the required Prisma query engine binary isn’t present in node_modules/.prisma/client. The repository already runs prisma generate in postinstall and build, but the Prisma generator configuration doesn't include the rhel-openssl-3.0.x binary target, so the platform-specific engine isn’t downloaded during generate.

Goal

Ensure Prisma generates and includes the correct Query Engine for rhel-openssl-3.0.x so that deployments do not fail with the "engine not found" error.

What to change

1. Modify prisma/schema.prisma generator block to explicitly request the rhel-openssl-3.0.x binary target (and keep native). The change will look like:

generator client {
provider = "prisma-client-js"
engineType = "binary"
binaryTargets = ["native", "rhel-openssl-3.0.x"]
}

Rationale: adding binaryTargets instructs Prisma to download the query engine binary for the specified platforms during prisma generate, ensuring the correct libquery_engine-*.so.node is placed under node_modules/.prisma/client.

2. Keep package.json postinstall script (already present) so engines are generated on install in CI/CD or Vercel. No change needed to package.json, but call out that deployments that use pnpm or other package managers must run prisma generate on install or use a build hook that runs it.

Testing steps (what the agent will do in the PR):

• Update prisma/schema.prisma as above.
• Run npx prisma generate locally to confirm the new binary target is fetched (can't run in PR, but will include changes only).
• Open a short PR with the change and a small note in the commit message.

Files to change

• prisma/schema.prisma: update generator client block to include engineType and binaryTargets.

Please create a pull request that makes this change in the repository Srijan76-code/vyne-ai.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
vyne-ai	Ready	Preview	Comment	Nov 17, 2025 9:25am