prisma | generation ORM for Node.js & TypeScript PostgreSQL | Database library

by prisma TypeScript Version: 3.12.0 License: Apache-2.0

Download this library from

kandi X-RAY | prisma Summary

prisma is a TypeScript library typically used in Database, MongoDB, PostgresSQL, MariaDB, DynamoDB applications. prisma has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

You can ask questions and initiate discussions about Prisma-related topics in the prisma repository on GitHub. 👉 Ask a question.

Support

Quality

Security

License

Reuse

kandi-support Support

prisma has a medium active ecosystem.
It has 22118 star(s) with 787 fork(s). There are 204 watchers for this library.
There were 10 major release(s) in the last 12 months.
There are 2037 open issues and 4064 have been closed. On average issues are closed in 83 days. There are 55 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of prisma is 3.12.0

prisma Support

Best in #Database

Average in #Database

prisma Support

Best in #Database

Average in #Database

quality kandi Quality

prisma has 0 bugs and 0 code smells.

prisma Quality

Best in #Database

Average in #Database

prisma Quality

Best in #Database

Average in #Database

security Security

prisma has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
prisma code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.

prisma Security

Best in #Database

Average in #Database

prisma Security

Best in #Database

Average in #Database

license License

prisma is licensed under the Apache-2.0 License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.

prisma License

Best in #Database

Average in #Database

prisma License

Best in #Database

Average in #Database

build Reuse

prisma releases are available to install and integrate.
Installation instructions, examples and code snippets are available.

prisma Reuse

Best in #Database

Average in #Database

prisma Reuse

Best in #Database

Average in #Database

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample Here

Get all kandi verified functions for this library.

prisma Key Features

If Prisma currently doesn't have a certain feature, be sure to check out the roadmap to see if this is already planned for the future.

prisma Examples and Code Snippets

See all related Code Snippets

The Prisma schema

Copy

Download

// Data source
datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

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

// Data model
model Post {
  id        Int     @id @default(autoincrement())
  title     String
  content   String?
  published Boolean @default(false)
  author    User?   @relation(fields:  [authorId], references: [id])
  authorId  Int?
}

model User {
  id    Int     @id @default(autoincrement())
  email String  @unique
  name  String?
  posts Post[]
}

Accessing your database with Prisma Client

Copy

Download

npm install @prisma/client

Reason: `object` ("[object Date]") cannot be serialized as JSON. Please only return JSON serializable data types

Copy

Download

// your data
let newsLetters = [
    {
        id: 'your-id',
        email: 'email@example.com',
        createdAt: new Date()
    }
];

// map the array
newsLetters.map(x => {
    x.createdAt = Math.floor(x.createdAt / 1000);
    return x;
})

// use newsLetters now
console.log(newsLetters);

for (const element of newsLetters) {
  element.createdAt = element.createdAt.toString()
}

How to create a custom health check for Prisma with @nestjs/terminus?

Copy

Download

    prisma.$queryRaw`SELECT 1`

import { Injectable } from "@nestjs/common";
import { HealthCheckError, HealthIndicator, HealthIndicatorResult } from "@nestjs/terminus";
import { PrismaService } from "./prisma.service";

@Injectable()
export class PrismaHealthIndicator extends HealthIndicator {
  constructor(private readonly prismaService: PrismaService) {
    super();
  }

  async isHealthy(key: string): Promise<HealthIndicatorResult> {
    try {
      await this.prismaService.$queryRaw`SELECT 1`;
      return this.getStatus(key, true);
    } catch (e) {
      throw new HealthCheckError("Prisma check failed", e);
    }
  }
}

Prisma using 1-1 and 1-n relation with same model

Copy

Download

model Product {
  id         String         @id @default(uuid()) @db.VarChar(36)
  image_id   String         @unique
  // image   ProductImage   @relation(name: "main_image", fields: [image_id], references: [id])
  image      ProductImage   @relation(name: "main_image", fields: [image_id], references: [id], onDelete: NoAction, onUpdate: NoAction)
  images     ProductImage[]
  slug       String         @unique(map: "slug") @db.VarChar(255)
  title      String         @db.VarChar(255)
  created_at DateTime       @default(now())
  updated_at DateTime       @default(now()) @updatedAt

  @@map("product")
}

model ProductImage {
  id                 String    @id @default(uuid()) @db.VarChar(36)
  src                String    @db.VarChar(255)
  created_at         DateTime  @default(now())
  updated_at         DateTime  @default(now()) @updatedAt
  product_id         String
  product            Product   @relation(fields: [product_id], references: [id])
  product_main_image Product[] @relation("main_image")

  @@map("product_image")
}

NX NestJs - Unexpected error: Error: Unable to load hasher for task "api:serve"

Copy

Download

"executor": "@nrwl/node:execute" -> "executor": "@nrwl/node:node"
"executor": "@nrwl/node:build" -> "executor": "@nrwl/node:webpack"

How to link many to many items in Prisma without duplicates

Copy

Download

model MenuProducts {
  menu_id Int
  menu Menu @relation(fields: [menu_id], references: [id])

  product_id Int
  product Product @relation(fields: [product_id], references: [id])


  created_at DateTime @default(now())
  updated_at DateTime @updatedAt

  @@map("menu_products")

  @@id([product_id, menu_id])

  @@unique([product_id, menu_id])
}

creating objects for 1:n relation with prisma

Copy

Download

model Fish {
    name      String      @id
    boardFish BoardFish? // removed autogenerated `[]` and made optional
}

model BoardFish {
    id       Int    @id @default(autoincrement())
    name     String
    fishType Fish   @relation(fields: [name], references: [name])
}

const fish = await prisma.boardFish.create({
  data: {
    fishType: {
      connect: { name: 'salmon' }, // or `connectOrCreate` if it doesn't exist
    },
  }
})

model Fish {
    name      String      @id
    boardFish BoardFish? // removed autogenerated `[]` and made optional
}

model BoardFish {
    id       Int    @id @default(autoincrement())
    name     String
    fishType Fish   @relation(fields: [name], references: [name])
}

const fish = await prisma.boardFish.create({
  data: {
    fishType: {
      connect: { name: 'salmon' }, // or `connectOrCreate` if it doesn't exist
    },
  }
})

When I run nest.js, I get a Missing "driver" option error

Copy

Download

@Module({
  imports: [
    GraphQLModule.forRoot<ApolloDriverConfig>({
      driver: ApolloDriver,
    }),
  ],
})

How to resolve 'getUserByAccount is not a function' in next-auth?

Copy

Download

npm uninstall next-auth @next-auth/prisma-adapter

npm install @next-auth/prisma-adapter

npm uninstall next-auth @next-auth/prisma-adapter

npm install @next-auth/prisma-adapter

Prisma client not marking property as null

Copy

Download

prisma-script> select id, "oauthData" from "User"
+---------+-------------+
| id      | oauthData   |
|---------+-------------|
| 124124  | null        |
| 1241241 | <null>      |
+---------+-------------+

Prisma, select row from table 1, depending on the latest foreign key in table 2

Copy

Download

    let publication = await prisma.publication.findFirst({
        where: {
            id
        },
        include: {
            publicationStatus: {
                orderBy: {
                    createdAt: 'desc'
                },
                take: 1
            }
        }
    });

    // check publication.publicationStatus[0].status and handle appropriately

See all related Code Snippets

Community Discussions

Trending Discussions on prisma

Reason: `object` ("[object Date]") cannot be serialized as JSON. Please only return JSON serializable data types
How to sample a PostgreSQL database using Prisma?
I need an advise about implementing a truncate option in endpoint
How to create a custom health check for Prisma with @nestjs/terminus?
Prisma using 1-1 and 1-n relation with same model
NX NestJs - Unexpected error: Error: Unable to load hasher for task "api:serve"
How to link many to many items in Prisma without duplicates
creating objects for 1:n relation with prisma
When I run nest.js, I get a Missing "driver" option error
How to resolve 'getUserByAccount is not a function' in next-auth?

Trending Discussions on prisma

QUESTION

Reason: `object` ("[object Date]") cannot be serialized as JSON. Please only return JSON serializable data types

Asked 2022-Mar-31 at 18:49

I am using prisma and Next.js. When I try to retrieve the content from prisma in getStaticProps it does fetch the data but I can't pass it on to the main component.

export const getStaticProps = async () => {
  const prisma = new PrismaClient();
  const newsLetters = await prisma.newsLetters.findMany();
  console.log(newsLetters);

  return {
    props: {
      newsLetters: newsLetters,
    },
  };
};

As you can see in this image it is fetching as well as printing the content.

But when I pass I get the following error for passing it as props

Reason: `object` ("[object Date]") cannot be serialized as JSON. Please only return JSON serializable data types.

ANSWER

Answered 2021-Dec-22 at 12:43

Looks like nextJS doesn't like serializing anything but scalar types for performance reasons. You can read more in this github issue. Best way you can handle this is that you convert your Date objects to UNIX timestamp before returning them.

// your data
let newsLetters = [
    {
        id: 'your-id',
        email: 'email@example.com',
        createdAt: new Date()
    }
];

// map the array
newsLetters.map(x => {
    x.createdAt = Math.floor(x.createdAt / 1000);
    return x;
})

// use newsLetters now
console.log(newsLetters);

Source https://stackoverflow.com/questions/70449092

QUESTION

Prisma using 1-1 and 1-n relation with same model

Asked 2022-Mar-08 at 11:45

In this case, a Product has many Image, and also has one main Image.

But when i run prisma format，throw Error:

error: Error validating field `image` in model `Product`: The relation field `image` on Model `Product` is missing an opposite relation field on the model `ProductImage`. Either run `prisma format` or add it manually.

my schema.prisma:

model ProductImage {
  id         String   @id @default(uuid()) @db.VarChar(36)
  product_id String
  product    Product  @relation(fields: [product_id], references: [id])
  src        String   @db.VarChar(255)
  created_at DateTime @default(now())
  updated_at DateTime @default(now()) @updatedAt

  @@map("product_image")
}

model Product {
  id         String         @id @default(uuid()) @db.VarChar(36)
  image_id   String
  image      ProductImage   @relation(name: "main_image", fields: [image_id], references: [id])
  images     ProductImage[]
  slug       String         @unique(map: "slug") @db.VarChar(255)
  title      String         @db.VarChar(255)
  created_at DateTime       @default(now())
  updated_at DateTime       @default(now()) @updatedAt

  @@map("product")
}

ANSWER

Answered 2022-Mar-08 at 11:45

This models should solve the issue:

model Product {
  id         String         @id @default(uuid()) @db.VarChar(36)
  image_id   String         @unique
  // image   ProductImage   @relation(name: "main_image", fields: [image_id], references: [id])
  image      ProductImage   @relation(name: "main_image", fields: [image_id], references: [id], onDelete: NoAction, onUpdate: NoAction)
  images     ProductImage[]
  slug       String         @unique(map: "slug") @db.VarChar(255)
  title      String         @db.VarChar(255)
  created_at DateTime       @default(now())
  updated_at DateTime       @default(now()) @updatedAt

  @@map("product")
}

model ProductImage {
  id                 String    @id @default(uuid()) @db.VarChar(36)
  src                String    @db.VarChar(255)
  created_at         DateTime  @default(now())
  updated_at         DateTime  @default(now()) @updatedAt
  product_id         String
  product            Product   @relation(fields: [product_id], references: [id])
  product_main_image Product[] @relation("main_image")

  @@map("product_image")
}

These references to relations in prisma schema should be helpful.

Source https://stackoverflow.com/questions/71363651

QUESTION

NX NestJs - Unexpected error: Error: Unable to load hasher for task "api:serve"

Asked 2022-Mar-06 at 04:58

i have been trying to follow these guide to learn NX, but i encounter this problem when i tried to serve the nestJs api you can see the complete code on this repo

nx serve api

i get these error

Error: Unable to resolve @nrwl/node:execute.
Cannot find executor 'execute' in /Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/@nrwl/node/executors.json.
at Workspaces.readExecutor (/Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/@nrwl/tao/src/shared/workspace.js:92:19)
at getExecutorForTask (/Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/@nrwl/workspace/src/tasks-runner/utils.js:135:22)
at getCustomHasher (/Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/@nrwl/workspace/src/tasks-runner/utils.js:140:25)
at TasksSchedule.<anonymous> (/Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/@nrwl/workspace/src/tasks-runner/tasks-schedule.js:114:62)
at Generator.next (<anonymous>)
at /Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/tslib/tslib.js:117:75
at new Promise (<anonymous>)
at __awaiter (/Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/tslib/tslib.js:113:16)
at TasksSchedule.hashTask (/Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/@nrwl/workspace/src/tasks-runner/tasks-schedule.js:113:38)
at TasksSchedule.<anonymous> (/Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/@nrwl/workspace/src/tasks-runner/tasks-schedule.js:58:24)

Unexpected error:
Error: Unable to load hasher for task "api:serve"
at getCustomHasher (/Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/@nrwl/workspace/src/tasks-runner/utils.js:145:15)
at TasksSchedule.<anonymous> (/Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/@nrwl/workspace/src/tasks-runner/tasks-schedule.js:114:62)
at Generator.next (<anonymous>)
at /Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/tslib/tslib.js:117:75
at new Promise (<anonymous>)
at __awaiter (/Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/tslib/tslib.js:113:16)
at TasksSchedule.hashTask (/Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/@nrwl/workspace/src/tasks-runner/tasks-schedule.js:113:38)
at TasksSchedule.<anonymous> (/Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/@nrwl/workspace/src/tasks-runner/tasks-schedule.js:58:24)
at Generator.next (<anonymous>)
at /Users/dariantvirgiesiswadie/Documents/pribadi/shirt-shop/node_modules/tslib/tslib.js:117:75

i follow the guide literally 1 to 1, same name and everything. so i suppose the problem is with my local machine (?) i running macOS 12.2.1 with M1 chip. or maybe these guide using some old version of nx (?) and something changed on the mean time?

so if anyone can give me a clue on this, would be very appreciated. thanks

edit :

i've try to follow the official Nest with NX demo from their website. and still got the same error when i try to nx serve api

ANSWER

Answered 2022-Mar-05 at 12:48

I use NX everyday on a mac with M1 chip and i never had such problems.

I think you should better use the last version of NX available with this tutorial on the NX website : NestJS with NX

Source https://stackoverflow.com/questions/71358644

QUESTION

How to link many to many items in Prisma without duplicates

Asked 2022-Feb-25 at 10:19

I have many to many relationships between Product and Menu.

model Product {
  id    Int    @id @default(autoincrement())
  name String
  price Float
  description String?
  product_category ProductCategory @relation(fields: [category_id], references: [id])
  category_id Int

  menus MenuProducts[]

  created_at DateTime @default(now())
  updated_at DateTime @updatedAt

  @@map("products")
}

model Menu {
  id    Int    @id @default(autoincrement())
  name String
  products MenuProducts[]

  created_at DateTime @default(now())
  updated_at DateTime @updatedAt
  @@map("menus")

}

model MenuProducts {
  menu_id Int
  menu Menu @relation(fields: [menu_id], references: [id])

  product_id Int
  product Product @relation(fields: [product_id], references: [id])


  created_at DateTime @default(now())
  updated_at DateTime @updatedAt

  @@map("menu_products")

  @@id([product_id, menu_id])
}

In the menu update, I want to assign many products to the menu.

I've tried like this:

this.prisma.menu.update({where: {id}, data: {...updateMenuDto, products: {connect: {id: 6}}}});

but I received this error:

The required connected records were not found. Expected 1 records to be connected after connect operation on one-to-many relation 'MenuToMenuProducts', found 0.

Anyway, I've tried like this:

this.prisma.menuProducts.create({data:{menu: {connect: {id: id}},product: {connect: {id: 6}}}})

and it worked, but on the second call I saw what the line was duplicated. How I can link multiple products to menu without inserting duplicates?

ANSWER

Answered 2022-Feb-25 at 10:19

To remove duplicates from the MenuProducts model you can define a unique constraint on the combination of product_id and menu_id which will restrict having duplication of product and menu id.

model MenuProducts {
  menu_id Int
  menu Menu @relation(fields: [menu_id], references: [id])

  product_id Int
  product Product @relation(fields: [product_id], references: [id])


  created_at DateTime @default(now())
  updated_at DateTime @updatedAt

  @@map("menu_products")

  @@id([product_id, menu_id])

  @@unique([product_id, menu_id])
}

Here is a reference of @@unique constraint.

Source https://stackoverflow.com/questions/71244606

QUESTION

creating objects for 1:n relation with prisma

Asked 2022-Feb-20 at 17:10

I have two models, Fish and BoardFish with a 1:1 relation - BoardFish is a type of Fish I created some seed Fish with named types.

how can I do this in Prisma? I think i have the schema setup, but inserting data isn't really documented apart from fancy/nested types.

schema:

model Fish {
    name      String      @id
    boardFish BoardFish[]
}

model BoardFish {
    id       Int    @id @default(autoincrement())
    name     String
    fishType Fish   @relation(fields: [name], references: [name])
}

try to create:

        let fishes = []
        for (let c = 0; c < fishCount; c++) {
            const fishType = await prisma.fish.findFirst({ where: { name: 'salmon' } })
            const fishData = {
                fishType: fishType!.name,
                // name: 'salmon',
                px: 0,
                py: 0,
            }
            const fish = await prisma.boardFish.create({ data: fishData })
            fishes.push(fish)
        }

but I'm unable to do the insertion:

→ 35 const fish = await prisma.boardFish.create({
       data: {
         fishType: 'salmon',
                   ~~~~~~~~
         px: 3,
         py: 5
       }
     })

Argument fishType: Got invalid value 'salmon' on prisma.createOneBoardFish. Provided String, expected FishCreateNestedOneWithoutBoardFishInput:
type FishCreateNestedOneWithoutBoardFishInput {
  create?: FishCreateWithoutBoardFishInput | FishUncheckedCreateWithoutBoardFishInput
  connectOrCreate?: FishCreateOrConnectWithoutBoardFishInput
  connect?: FishWhereUniqueInput
}

The types involved are pretty hard to follow, Prisma seems to really take the cake for most "magic" with thousands of lines of auto generated code, which I've been digging through without much luck.

ANSWER

Answered 2022-Feb-20 at 17:10

If you want to have 1:1 relations, I think the schema needs to look more like this:

model Fish {
    name      String      @id
    boardFish BoardFish? // removed autogenerated `[]` and made optional
}

model BoardFish {
    id       Int    @id @default(autoincrement())
    name     String
    fishType Fish   @relation(fields: [name], references: [name])
}

When creating a related record, use prisma's connect api

const fish = await prisma.boardFish.create({
  data: {
    fishType: {
      connect: { name: 'salmon' }, // or `connectOrCreate` if it doesn't exist
    },
  }
})

Source https://stackoverflow.com/questions/71195586

QUESTION

When I run nest.js, I get a Missing "driver" option error

Asked 2022-Feb-19 at 12:43

I am using nest.js, prisma, and graphql.
When I run the npm run start:dev command, I get an error.
If anyone knows how to solve this, please let me know.

ERROR [GraphQLModule] Missing "driver" option. In the latest version of "@nestjs/graphql" package (v10) a new required configuration property called "driver" has been introduced. Check out the official documentation for more details on how to migrate (https://docs.nestjs.com/graphql/migration-guide). Example:

GraphQLModule.forRoot({ driver: ApolloDriver, })

app.module.ts
import { Module } from '@nestjs/common';
import { GraphQLModule } from '@nestjs/graphql';
import { AppController } from './app.controller';
import { AppService } from './app.service';
import { ApolloServerPluginLandingPageLocalDefault } from 'apollo-server-core';
import { DonationsModule } from './donations/donations.module';

@Module({
  imports: [
    GraphQLModule.forRoot({
      playground: false,
      plugins: [ApolloServerPluginLandingPageLocalDefault()],
      typePaths: ['./**/*.graphql'],
    }),
    DonationsModule,
  ],
  controllers: [AppController],
  providers: [AppService],
})
export class AppModule {}

generate-typings.ts
import { GraphQLDefinitionsFactory } from '@nestjs/graphql';
import { join } from 'path';

const definitionsFactory = new GraphQLDefinitionsFactory();
definitionsFactory.generate({
  typePaths: ['./src/**/*.graphql'],
  path: join(process.cwd(), 'src/graphql.ts'),
  outputAs: 'class',
  watch: true,
});

fix

@Module({
  imports: [
    GraphQLModule.forRoot<ApolloDriverConfig>({
      driver: ApolloDriver,
      autoSchemaFile: true,
      plugins: [ApolloServerPluginLandingPageLocalDefault()],
      typePaths: ['./**/*.graphql'],
    }),
    DonationsModule,
  ],
  controllers: [AppController],
  providers: [AppService],
})

ANSWER

Answered 2022-Feb-19 at 12:36

Checkout the nestjs/graphql documentation page and the other link that you have mentioned. You have to configure your GraphQLModule like this which I don't see in your code.

@Module({
  imports: [
    GraphQLModule.forRoot<ApolloDriverConfig>({
      driver: ApolloDriver,
    }),
  ],
})

Source https://stackoverflow.com/questions/71183677

QUESTION

How to resolve 'getUserByAccount is not a function' in next-auth?

Asked 2022-Feb-12 at 05:28

I've updated Nextjs to it's newest version and also updated next-auth and the prisma adapter as specified by the docs.

However, when I try to authenticate in the app with signIn I get the following error with the latest updates:

[next-auth][error][OAUTH_CALLBACK_HANDLER_ERROR] 
https://next-auth.js.org/errors#oauth_callback_handler_error getUserByAccount is not a function {
  message: 'getUserByAccount is not a function',
  stack: 'TypeError: getUserByAccount is not a function\n' +
    '    at Object.callback (/home/.../node_modules/next-auth/core/routes/callback.js:81:39)\n' +
    '    at runMicrotasks (<anonymous>)\n' +
    '    at processTicksAndRejections (internal/process/task_queues.js:95:5)\n' +
    '    at async NextAuthHandler (/home/.../node_modules/next-auth/core/index.js:103:28)\n' +
    '    at async NextAuthNextHandler (/home/.../node_modules/next-auth/next/index.js:40:7)\n' +
    '    at async /home/nik/dev/lugredu/node_modules/next-auth/next/index.js:80:32\n' +
    '    at async Object.apiResolver (/home/.../node_modules/next/dist/server/api-utils.js:102:9)\n' +
    '    at async DevServer.handleApiRequest (/home/.../node_modules/next/dist/server/next-server.js:1014:9)\n' +
    '    at async Object.fn (/home/.../node_modules/next/dist/server/next-server.js:901:37)\n' +
    '    at async Router.execute (/home/.../node_modules/next/dist/server/router.js:210:32)',
  name: 'TypeError'
}

Is there something I'm doing wrong, or is there an incompatibility I'm missing?

Relevant package.json:

...
    "@next-auth/prisma-adapter": "^0.5.2-next.19",
    "next": "^12.0.3",
    "next-auth": "4.0.0-beta.6",
    "prisma": "^3.4.1",
...

[...nextauth].ts:

import NextAuth from 'next-auth';
import CognitoProvider from 'next-auth/providers/cognito';
import { PrismaAdapter } from '@next-auth/prisma-adapter';
import { PrismaClient } from '@prisma/client';

const prisma = new PrismaClient();

export default NextAuth({
  adapter: PrismaAdapter(prisma),
  providers: [
    CognitoProvider({
      clientId: process.env.COGNITO_CLIENT_ID,
      clientSecret: process.env.COGNITO_CLIENT_SECRET,
      issuer: process.env.COGNITO_ISSUER,
    }),
  ],

  callbacks: {
    async session({ session, user }) {
      session.userId = user.id;
      session.role = user.role;
      return Promise.resolve(session);
    },
  },
});

ANSWER

Answered 2022-Jan-21 at 13:13

In the NextAuth.JS 4.0 the "Prisma schema" have slightly changed.

From the upgrade guide:

created_at/createdAt and updated_at/updatedAt fields are removed from all Models.

user_id/userId consistently named userId.

compound_id/compoundId is removed from Account.

access_token/accessToken is removed from Session.

email_verified/emailVerified on User is consistently named email_verified.

provider_id/providerId renamed to provider on Account

provider_type/providerType renamed to type on Account

provider_account_id/providerAccountId on Account is consistently named providerAccountId

access_token_expires/accessTokenExpires on Account renamed to expires_in

New fields on Account: expires_at, token_type, scope, id_token, session_state

verification_requests table has been renamed to verification_tokens

Complete new schema in: https://next-auth.js.org/adapters/prisma

Source https://stackoverflow.com/questions/69899392

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install prisma

The fastest way to get started with Prisma is by following the Quickstart (5 min).
Add Prisma to an existing project
Setup a new project with Prisma from scratch
Prisma Tests Status:
E2E Tests Status: