Prisma 6.16.0 — `dmmf` shape changed: `documentation` missing and field-encryption breaks in `prisma-client-js`

[Lqm1]

Starting with Prisma v6.16.0, Prisma appears to have removed its Rust dependency.
Reference: https://github.com/prisma/prisma/releases/tag/6.16.0

After upgrading, the shape of dmmf returned by the new client seems to have changed. As a result:

• Zod validation fails because isList, isUnique, and isId are no longer present on fields.
• documentation also appears to be missing or no longer accessible via dmmf.

I patched the package to avoid the Zod errors, but I still cannot load documentation. Because of this, field encryption no longer works.

This problem occurs when using prisma-client-js (not prisma-client). prisma-client recommends using @prisma/internals as a workaround, but including @prisma/internals pulls a WASM file into the package and that causes errors in some web frameworks (bundling/runtime issues).

Steps to reproduce

1. Upgrade Prisma to 6.16.0 (or later).
2. Generate the client and inspect dmmf from prisma-client-js.
3. Attempt to read field.documentation (or run code that expects isList, isUnique, isId).
4. Observe Zod validation / field-encryption code failing and documentation being unavailable.

Actual behavior

• dmmf no longer contains isList, isUnique, or isId for fields.
• documentation is not accessible via dmmf.
• Workarounds that import @prisma/internals introduce WASM which breaks bundling/runtime in some web frameworks.
• Field encryption fails because it cannot determine which fields have documentation/metadata.

Workarounds tried

• Rewrote the package to bypass the missing isList/isUnique/isId checks — still cannot access documentation.
• Using @prisma/internals (suggested by prisma-client) — this causes errors in some web frameworks due to the WASM file being included.

Example

dmmf

{
    "datamodel":{
        "models":[
            {
                "name":"User",
                "fields":[
                    {
                        "name":"id",
                        "kind":"scalar",
                        "type":"String"
                    },
                    {
                        "name":"name",
                        "kind":"scalar",
                        "type":"String"
                    },
                    {
                        "name":"email",
                        "kind":"scalar",
                        "type":"String"
                    },
                    {
                        "name":"emailVerified",
                        "kind":"scalar",
                        "type":"Boolean"
                    },
                    {
                        "name":"image",
                        "kind":"scalar",
                        "type":"String"
                    },
                    {
                        "name":"role",
                        "kind":"scalar",
                        "type":"String"
                    },
                    {
                        "name":"banned",
                        "kind":"scalar",
                        "type":"Boolean"
                    },
                    {
                        "name":"banReason",
                        "kind":"scalar",
                        "type":"String"
                    },
                    {
                        "name":"banExpires",
                        "kind":"scalar",
                        "type":"DateTime"
                    },
                    {
                        "name":"stripeCustomerId",
                        "kind":"scalar",
                        "type":"String"
                    },
                    {
                        "name":"chatwootSourceId",
                        "kind":"scalar",
                        "type":"String"
                    },
                    {
                        "name":"createdAt",
                        "kind":"scalar",
                        "type":"DateTime"
                    },
                    {
                        "name":"updatedAt",
                        "kind":"scalar",
                        "type":"DateTime"
                    }
                ]
            }
        ]
    }
}

schema.prisma

model User {
  id               String          @id
  name             String
  email            String          @unique
  emailVerified    Boolean
  image            String?
  role             String?
  banned           Boolean?
  banReason        String?
  banExpires       DateTime?
  stripeCustomerId String?
  chatwootSourceId String?
  createdAt        DateTime
  updatedAt        DateTime
}

[franky47]

Thanks, it looks like with these versions, we might have to configure the extension differently.

It's a shame, having the single source of truth in the schema file was a nice DX (albeit at the expense of readability if you push the concept too far).

Unfortunately I don't have a ton of time to spend on this package (most of my clients don't use Prisma, and most of my OSS time is focused on nuqs at the moment).

If someone wants to discuss alternative ways where we could pass a type-safe configuration to this extension (ie: if you change the schema, the extension configuration should know about it), feel free to make suggestions, and I'll happily review PRs.

[Lqm1]

Thanks, it looks like with these versions, we might have to configure the extension differently.

It's a shame, having the single source of truth in the schema file was a nice DX (albeit at the expense of readability if you push the concept too far).

Unfortunately I don't have a ton of time to spend on this package (most of my clients don't use Prisma, and most of my OSS time is focused on nuqs at the moment).

If someone wants to discuss alternative ways where we could pass a type-safe configuration to this extension (ie: if you change the schema, the extension configuration should know about it), feel free to make suggestions, and I'll happily review PRs.

Relying on the Prisma package to get the schema would be doomed by changes like this, so how about reading schema.prisma directly?
It has been adopted by projects such as Better-Auth.
Reference: https://github.com/better-auth/better-auth/blob/canary/packages/cli/src/generators/prisma.ts

https://github.com/MrLeebo/prisma-ast

[franky47]

Oh yeah that could work, as long as it supports reading multiple schema files and other Prisma features.

It's a shame that, with the move from Prisma to a pure TypeScript engine, we don't have an even easier access to the same schema parsing facilities as what they use in core.

[Lqm1]

Oh yeah that could work, as long as it supports reading multiple schema files and other Prisma features.

It's a shame that, with the move from Prisma to a pure TypeScript engine, we don't have an even easier access to the same schema parsing facilities as what they use in core.

I tried to implement my idea once.
This method may not be the best, so please check it once.

#144

[regis-underdog]

Is there any way to address this issue? The PR mentioned seems close; we are nearing the Prisma v7 release which means that people using field encryption will not be able to upgrade when that happens.

[geosigno]

+1 👍