"Property does not exist" when I want to use model added in Prisma.schema

Question

I'm working on ReactJS project with NextJS Framework and Prisma to manage connection and queries to the DB.

On my local project the Support model is found and when I use it in my API and build my project it's ok.

But when I push my project on production server (Plesk), the build shows me this typescript error because it doesn't find the Support model:

./src/pages/api/support/index.ts:27:26
Type error: Property 'support' does not exist on type 'PrismaClient<PrismaClientOptions, never, RejectOnNotFound | RejectPerOperation | undefined>'.

The path ./src/pages/api/support/index.ts is where I want to use the Support model

My prisma.schema:

datasource db {
  provider = "mysql"
  url      = env("DATABASE_CONNECTION")
}

generator client {
  provider = "prisma-client-js"
}

model User {
  id              Int       @id @unique @default(autoincrement())
  gender          String?
  firstName       String
  lastName        String
  email           String    @unique
  phone           String
  birthday        DateTime?
  income          Float?
  pincode         Int?
  points          Float?
  token           String    @db.Text
  ipAddress       String
  kyc             Kyc[]
  createdAt       DateTime  @default(now())
  updatedAt       DateTime?
  isValidated     Boolean   @default(false)
  roleId          Int
  role            Role      @relation(fields: [roleId], references: [id])
  Alerts          Alerts[]
  Support Support[]
}

model Kyc {
  id        Int       @id @unique @default(autoincrement())
  name      String
  validated Boolean   @default(false)
  path      String
  createdAt DateTime  @default(now())
  updatedAt DateTime? @updatedAt
  user      User      @relation(fields: [userId], references: [id])
  userId    Int
}

model Alerts {
  id         Int      @id @unique @default(autoincrement())
  type       TYPE     @default(NOBLOCKED)
  message    String   @db.Text
  transferId Int      @unique
  fromUserId Int
  read       Boolean  @default(false)
  createdAt  DateTime @default(now())
  user       User     @relation(fields: [fromUserId], references: [id])
}

model Role {
  id   Int    @id @unique @default(autoincrement())
  name String
  User User[]
}

model Support {
  id        Int     @id @unique @default(autoincrement())
  subject   String
  message   String  @db.Text
  createdAt DateTime  @default(now())
  userId          Int
  user            User      @relation(fields: [userId], references: [id])
}

enum TYPE {
  BLOCKED
  NOBLOCKED
}

I don't know if I need to use prisma migrate dev or prisma migrate deploy each time I push the latest changes.

Sailer

Did you ran prisma generate to generate Prisma client after making changes on Prisma schema ? prisma migrate dev will also generate Prisma client along with migration. – Schizogenesis

In addition to what @PasinduDilshan mentioned (which is a likely cause of the problem), is this issue only with the Support model? Do all other models work as expected? – Ciaphus

@TasinIshmam yes every other models worked properly. This error has been only for Support model because I had already pushed news models to the production server and I never had this type of error. This could be because I just started to use prisma migrate deploy with this Support model. And this is exactly what @Pasindudilshan said with the prisma migrate dev which also generates Prisma client and why I never had this error before. – Sailer

Yes, prisma migrate deploy does not generate the client, so you have to run prisma generate as was mentioned. Just to clarify, you have been able to solve the problem now? – Ciaphus

Yes everything works fine ! Thanks you guys for your help ! – Sailer

Also If you use VS Code sometimes you need to restart TS server,, – Mantle

If anyone has this issue in WebStrom/IntelliJ: add a new JS library pointing to node_modules/@prisma/client in IDE settings (Languages & Frameworks -> JavaScript -> Libraries -> Add...) – Chabot

Answer 1

I tried prisma generate and prisma migrate dev but was still having the same error. I had to restart VSCode and everything is working fine now

Consumer

If you are using Typescript, open up the Command Palette (Ctrl Shift P), and typing "Restart Typescript Server", and press enter. Would help as well, without the need to restart VSCode – Interjoin

I remember that I had the same problem and fixed it with that, but now it doesn't work anymore on any device after restarts and it won't build, so not a vscode issue this time. What now?? – Luckily

running $ prisma generate worked for me. I read through the documentation and ideally prisma generate should be executed every time you make changes in the prisma.schema file. Here's the reference prisma.io/docs/concepts/components/… – Monogenesis

Or simply open the file ./node_modules/.prisma/client/index.d.ts – Haugh

Answer 2

I forgot to await

const user = prisma.user.findUnique({ 
  where: {
    userId: authorUserId
  },
  select: {
    id: true
  }
})

but should be:

const user = **await** prisma.user.findUnique({ 
  where: {
    userId: authorUserId
  },
  select: {
    id: true
  }
})

Purpurin

Answer 3

Restart your typescript server in VSCode CTRL + SHIFT + P then type: restart TS Server

Killie

i'ts works perfect for me – Maggie

Answer 4

I have restarted my Visual Studio code and it started working fine.

Materse

Answer 5

Try to run npx prisma generate. The model should then be in the prisma client. However if not, try ctrl + P then type in > reload window in the vs code command palette and hit the reload window option. That should solve the issue

Dana

Answer 6

used prisma generate command but still, the schemas were marked as red. I had to restart my web storm IDE to get it fixed.

Missi

Answer 7

I tried everything, even reinstalling prisma client. What worked for me was recreating the migration.

Longer

Answer 8

Simply open the file ./node_modules/.prisma/client/index.d.ts.

This file contains the types generated. Opening it instantly triggers typescript to update those types.

Haugh

Answer 9

I made a silly mistake by extending PrismaClient class in

❌ prisma.module.ts

export class PrismaModule extends PrismaClient {}

✅ prisma.service.ts

@Injectable()
export class PrismaService extends PrismaClient {}

Vacuum

Answer 10

My issue was that the prisma client references the model names but as camelCase, whereas they're defined in the schema using PascalCase. This threw me because most of my model names are single words so where I'd defined a model name like User in the schema and added @@map("user") to the definition, I had the impression that when I did something like await prisma.user.delete({ ... the model/ table name user was lowercase as a result of the @@map declaration, but it turns out it isn't, rather prisma takes the model name and makes the first letter lowercase, and hence why for my model name OTP (with @@map("otp)) I have to use it like prisma.oTP.delete({ ...

Monniemono

Answer 11

stop the local server, run npx prisma generate, start the server again in order to generate the prisma model in /node_modules/.prisma/client/index.d.ts which contains property that can be accessed by prisma instance.

Mapp

Thanks, this worked. Is there a way to avoid doing this? I know every platform and ecosystem has its quirks, but this is just as annoying as Python's package management systems – Yearbook

Answer 12

In my case, I created a schema named Post, but I called await prisma.posts. It should be called await prisma.posts. Make sure you don't make Typo. 😅

Portie

Answer 13

Note! I'm only refer to the title of the question and not to the content. This error also can be raised also when you don't working with the right node version like in situation when using nvm with old node version.

Emblaze

Answer 14

Just Restart VSCode, it works magic!!!.

if above solution not worked, try this solution

Nigger