prisma: prisma@4.7.1 - "RangeError: Maximum call stack size exceeded" when clientExtensions enabled

Same issue hear without even using $extends just upgrading to 4.8.0 crashes our compilation.

Confirmed this still exists in 4.8.0. $extends client method triggers this, as does Prisma.defineExtension.

Hey @lipis @mattbajorek, sorry that you’re still experiencing this. We’ve fixed and tested the original reproduction case, but it seems there is more to it. Could you please provide us with a reproduction?

Update: Nevermind, I could reproduce it with a more complex schema

I installed the 4.8.0 and still have the issue when building a Next.js app with $extends

I’m having this same error too. For me it only happens when I actually try to use an extension not just enabling it.

export const DBConn = new PrismaClient({ log: [ { emit: 'event', level: 'query', }, { emit: 'stdout', level: 'error', }, { emit: 'stdout', level: 'info', }, { emit: 'stdout', level: 'warn', }, ], }).$extends({ name: 'user display name', result: { users: { displayName: { needs: { first_name: true, preferred_name: true }, compute(user) { return user.preferred_name || user.first_name; }, }, }, }, });

If I remove the .$extension part, everything works just fine. Starting it with ts-node.

[nodemon] watching extensions: ts,json [nodemon] starting ts-node ./src/api.ts /Users/ajholloway/programming/nectarbackend/node_modules/typescript/lib/typescript.js:66937 outofbandVarianceMarkerHandler = function (onlyUnreliable) { ^ RangeError: Maximum call stack size exceeded at outofbandVarianceMarkerHandler (/Users/ajholloway/programming/nectarbackend/node_modules/typescript/lib/typescript.js:66937:63)

Hey @TaylorFacen, thanks for the report. Could you please create a separate issue?

Done! https://github.com/prisma/prisma/issues/17349 . Let me know if you need any additional information.

Thanks to your help 4.9.0-integration-feat-client-ext-generic-type-api.13, should fix the export issue as well as the node inference issue @khalil-omer. Could you please give it a try? I am not 100% for you @Multiply since I was not able to reproduce this exact same error. If the issue persists, would you mind sending me your schema? As for the nested includes issue, I will fix it but treat it as a separate issue.

Many thanks for the help so far 👍

@millsp this latest error appears to be related to declarations: true and declerationMaps: true. If I set both properties to false in the tsconfig, the error disappears and the build is successful.

As someone commented here, there is an outstanding bug with declarations. Maybe there should be a separate issue created for that.

Hey @beeman, I think we’ve had another report of this here.

@millsp Hi - looks like you are making progress with this. With your branch installed, the call stack error is gone and Prisma.defineExtension throws no tsc errors. However, $extends is now throwing the following error instead.

Exported variable 'pivotPrisma' has or is using name 'Payload' from external module "[path]/client/runtime/index" but cannot be named.

The above error is actually throwing many times. Not sure if that fact helps you debug.

@millsp in case you still need my use case… here is what I did with $extend in my Next.js project: https://gist.github.com/lipis/7564e99b6315a3940dbcb1a5c1a413a9

@JoeKarow I believe @tavindev has shared his schema in the issue description - JoeKarow/prisma4.7.1-reproduce@main/prisma/schema.prisma

That’s my schema 😄