Prisma 7.10 is safe to commit the generated/prisma client?

[DarkKingpro10]

In the last versions of Prisma it was recommended to not commit the generated code of Prisma Client, but in the new version of Prisma Next V8 and Prisma 7.10 it is safe?
I understand that there is a Discussions where it was recommended to not commit the generated/prisma.

But now in 2026 it is Rust free so why is it not recommended?

[paramjeetn]

The recommendation still stands: you should NOT commit the generated/prisma client folder to git, even with the modern TypeScript-only / Rust-free query engine architecture.

Why you should keep it in .gitignore and generate in CI/CD:

1. Schema Synchronization:
   If a developer alters schema.prisma or pulls a branch without committing the freshly generated files, your committed client becomes out-of-sync with the schema, leading to confusing runtime typing mismatches.

2. Repository Size & Noise:
   Generated client files can contain thousands of lines of verbose D.TS type definitions and boilerplate. Committing them creates massive git diff noise on every minor schema tweak or version upgrade.

3. Deterministic CI/CD Pipeline:
   The official and idiomatic practice is to run prisma generate in your postinstall script (or CI build step):

// package.json
{
  "scripts": {
    "postinstall": "prisma generate",
    "build": "next build"
  }
}

This ensures every machine (local dev, Docker containers, Vercel/Render deployments) generates the exact client matching the installed @prisma/client version on the fly.

[Pleo2]

The Rust-free architecture changes what can be generated, but it does not by itself change the source-control recommendation.

Prisma's current generator reference still explicitly says to exclude the generated directory from version control. The main reason is that the generated output may include a platform-specific query engine unless you use engineType = "client". Prisma's v7 generation guide also recommends regenerating after schema or generator changes, commonly in postinstall or before the production build:

• https://www.prisma.io/docs/orm/prisma-schema/overview/generators#prisma-client
• https://www.prisma.io/docs/orm/v7/prisma-client/setup-and-configuration/generating-prisma-client#when-to-run-generate

For a normal application on Prisma 7.10, I would therefore keep this committed:

• schema.prisma
• migrations
• prisma.config.ts
• the package-manager lockfile

and keep generated/prisma ignored, with prisma generate in CI/build.

If you explicitly use engineType = "client", the Rust-binary portability concern disappears, so committing the output can be technically safe when a deployment environment cannot run generation. It is still a deliberate trade-off: larger/noisier diffs and a risk of the generated client drifting from the schema or installed Prisma version. In other words, Rust-free makes committing more portable; it does not make it the recommended default workflow.