nexus-prisma VS typegraphql-prisma

Defining the exposed GraphQL schema will often involve re-creating our Prisma models using Nexus types, which can be tedious and error-prone. By using the official Prisma plugin for Nexus, we can easily project models from the data layer unto GraphQL types in our API layer.

Indeed, with nexus-prisma you can easily construct your GraphQL schema based on your database schema.

I like nexus with prisma better. I feel like typegraphql shines the most when using with orms like MikroORM of TypeORM. Though prisma with typegraphql is not a bad idea, there's a cool plugin that can generate crud resolvers.

I think Prisma is not only modern ORM. If we want to build a GraphQL api, it will help us boost our work. We don't have to waste our time to make CRUD operations, we just define Prisma model and it will do it for us: https://github.com/MichalLytek/typegraphql-prisma/blob/main/Readme.md

Prisma works well with TypeGraphQL. In fact, there's a generator that makes it easier to generate TypeGraphQL types and CRUD resolvers from your Prisma 2 schema: https://github.com/MichalLytek/typegraphql-prisma

There are also several tools that allow you generate a GraphQL CRUD API based on Prisma, such as Amplication, KeystoneJS or typegraphql-prisma.

Learn more about other advanced operations you can apply to your GraphQL resolvers, such as custom resolvers, authorization, middleware and additional decorators to your Prisma schema and models here.