Prisma Client errors with "TypeError: Cannot create proxy with a non-object as target or handler" when using result client extension with no needs and count method

[semoal]

Bug description

Just upgraded to 5.1.0, and after adjusting the Array shortcut breaking change, I have run the testing suite and this test fails, I'm not quite sure how to debug this.

Any help or question is appreciated and I would love to help.

 FAIL  src/controllers/v1/users.controller.test.ts > Users > Search > should search
TypeError: Cannot create proxy with a non-object as target or handler
 ❯ xe ../../packages/prisma-client/client/runtime/library.js:26:5353
 ❯ Ds ../../packages/prisma-client/client/runtime/library.js:112:2696
 ❯ visitor ../../packages/prisma-client/client/runtime/library.js:112:3823
 ❯ $r ../../packages/prisma-client/client/runtime/library.js:112:3062
 ❯ Is ../../packages/prisma-client/client/runtime/library.js:112:3751
 ❯ l ../../packages/prisma-client/client/runtime/library.js:126:10330
 ❯ search src/controllers/v1/users.controller.ts:149:17
    147|     : { name: Prisma.SortOrder.asc };
    148|
    149|   const count = await prisma.user.count();

Our User schema is quite big so it's complicated to share.

I'm using Postgres, Node 18.13.0, Typescript 5.0.4 and a PNPM monorepo if it helps.

How to reproduce

Expected behavior

No response

Prisma information

// Add your schema.prisma

// Add your code using Prisma Client

Environment & setup

• OS: Macosx
• Database: Postgresql
• Node.js version: 18.13.0

Prisma Version

5.1.0

[janpio]

Can you please share the actual code that is being executed there?
Did I understand correctly that you upgraded from 4.x to 5.1 directly and now get this error?

[semoal]

Yes, exactly;

The code is something as simply as calling that model with count:

export async function search(
  params: SearchParams
): TypedPaginatedResponse<(User & { onboarding: { id: string } | null })[]> {
  const count = await prisma.user.count();

  return {
    data: [],
    pagination: {
      count: [].length,
      totalCount: count,
    },
  };
}

And the test with Vitest:

    it<TestContext>("should search", async () => {
      const r = await search(defaultPagination);
      expect(r.data.length).toBeGreaterThan(0);
    });

[semoal]

The previous version I was of Prisma its: 4.15.0, and Vitest I'm using 0.34.1 (latest) but tried with 0.32.0 and got the same error;

Btw; it's only happening on this model, because I run different tests on other models.count() and works fine.

This is the User model, if it helps:

model User {
  id                 String       @id @default(uuid()) @db.Uuid
  email              String?
  name               String?
  surname            String?
  avatar             String?
  externalId         String?
  ssn                String?
  loginMethod        LoginMethod?
  accessControlList  String[]
  createdAt          DateTime     @default(now()) @db.Timestamptz(3)
  updatedAt          DateTime     @updatedAt @db.Timestamptz(3)
  deactivatedAt      DateTime?    @db.Timestamptz(3)
  registeredAt       DateTime?    @db.Timestamptz(3)
  status             UserStatus?
  /// Optional to allow returning null when we send users to the front-end
  passwordSalt       String?
  /// Optional to allow returning null when we send users to the front-end
  password           String?
  entityId           String?      @db.Uuid
  passwordExpired    Boolean?
  userType           UserType     @default(ADVISOR_FF)
  defaultRole        UserRole     @default(ADVISOR)
  isBlind            Boolean?
  isElderly          Boolean?
  hasChildTaxCredit  Boolean?
  hasDependentCredit Boolean?

  middleName             String?
  birthDate              DateTime?       @db.Timestamptz(3)
  retirementDate         DateTime?       @db.Timestamptz(3)
  retirementAge          Int?
  numberOfDependents     Int?
  riskLevel              Int?
  investmentObjective    Int?
  countryOfCitizenshipId String?
  countryOfResidenceId   String?
  prefix                 Prefix?
  sufix                  Sufix?
  gender                 Gender?
  maritalStatus          MaritalStatus?
  marketFeel             MarketFeelings?
  riskId                 String?         @db.Uuid
  currentRisk            Risk?           @relation("userRisk", fields: [riskId], references: [id])
  dependent              Boolean?

  authenticationMethod AuthenticationMethods?
  authenticationSecret String?
  addresses            UserAddresses[]
  documents            UserDocuments[]
  phones               UserPhones[]
  portfolios           Portfolio[]
  advisorOnboardings   Onboarding[]           @relation("advisorOnboardings")
  countryOfResidence   Country?               @relation("countryOfResidence", fields: [countryOfResidenceId], references: [id])
  entity               Entity?                @relation(fields: [entityId], references: [id], onDelete: Cascade)
  countryOfCitizenship Country?               @relation("countryOfCitizenship", fields: [countryOfCitizenshipId], references: [id])
  holders              Holder[]
  benchmarks           Benchmark[]
  modelPortfolios      ModelPortfolio[]
  strategies           Strategy[]
  onboarding           Onboarding?
  activities           UserActivity[]
  taskUsers            UsersOnTasks[]
  guestGroupMembers    GroupMembers[]
  plaidExtraData       PlaidExtraData[]
  amount               Float?
  risks                Risk[]
  simpleIntegrations   Json?

  integrationStatus                IntegrationStatus?
  errorCode                        String?
  errorMessage                     String?
  riskProfile                      RiskProfile[]
  metadata                         Metadata[]
  quickViews                       QuickView[]
  factFinderTemplates              FactFinderTemplate[]
  userFactFinderCampaigns          FactFinderCampaign[]
  advisorFactFinderCampaigns       FactFinderCampaign[]              @relation(name: "advisorCampaigns")
  rebalancings                     Rebalancing[]
  taskHistories                    TaskHistory[]                     @relation("taskHistoryUser")
  affectingTaskHistories           TaskHistory[]                     @relation("userAffected")
  taskAttachments                  TaskAttachment[]
  taskComments                     TaskComment[]
  tasks                            Task[]
  mailingTemplates                 MailingTemplates[]
  collaboratingFactFinderCampaigns FactFinderCampaignCollaborators[]
  userDevices                      UserDevices[]
  assets                           Asset[]
  liabilities                      Liability[]
  expenses                         Expense[]
  factFinderCampaignFeedback       FactFinderCampaignFeedback[]
  integrations                     UserIntegration[]
  incomes                          Income[]
  insurances                       Insurance[]
  estates                          Estate[]
  liabilityAmortizations           LiabilityAmortization[]
  userGoals                        Goal[]                            @relation("retirementUser")
  headGoals                        Goal[]                            @relation("retirementAgeHead")
  spouseGoals                      Goal[]                            @relation("retirementAgeSpouse")
  taxDetails                       TaxDetail[]

  @@index([amount])
  @@index([name])
  @@index([email])
  @@index([userType])
}

It's big but worked previously fine, so dunno

[janpio]

The error message also mentions : { name: Prisma.SortOrder.asc };, while the code you shared does not. Might that be relevant?

Can you maybe isolate the schema and code into its own, standalone project so you can see if you can reproduce it? Sharing that project with us would be perfect for us to reproduce, understand and hopefully fix.

[semoal]

The error message also mentions : { name: Prisma.SortOrder.asc };, while the code you shared does not. Might that be relevant?

Can you maybe isolate the schema and code into its own, standalone project so you can see if you can reproduce it? Sharing that project with us would be perfect for us to reproduce, understand and hopefully fix.

I'll try to isolate but it's a large repo so it's a bit complex, but will try for sure.
About the Prisma.SortOrder.asc, was not relevant tried with the code I've pasted here and got the same error.

[semoal]

Got it guys!
I've had this, basically we hide the password and salt for every request we do through the default prisma singleton:

const _prisma = getPrismaClient();
const prisma = _prisma.$extends({
  result: {
    user: {
      password: {
        needs: {},
        compute() {
          return "";
        },
      },
      passwordSalt: {
        needs: {},
        compute() {
          return "";
        },
      },

On 4.5.1 worked without the needs of specifying the field, after specifying the needs: { field: true }, worked like a charm!

const prisma = _prisma.$extends({
  result: {
    user: {
      password: {
        needs: { password: true },
        compute() {
          return "";
        },
      },
      passwordSalt: {
        needs: { passwordSalt: true },
        compute() {
          return "";
        },
      },

Hope this issue it's hopeful for someone that forgot to add that, and the error is not self-descriptive at all -- I know it's complex but hehe

[SevInf]

Reopening, since it is an actual bug in 5.1. Even though there is a workaround for it (thank you for providing it, @semoal ), we need to fix it.

[SevInf]

Fix released in 5.1.1