nexus VS nexus-plugin-prisma

Compare nexus vs nexus-plugin-prisma and see what are their differences.

nexus

Code-First, Type-Safe, GraphQL Schema Construction (by graphql-nexus)
Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
nexus nexus-plugin-prisma
4 3
3,363 833
0.1% 0.0%
1.1 0.0
4 months ago 2 days ago
TypeScript TypeScript
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

nexus

Posts with mentions or reviews of nexus. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-12-19.
  • What to use with Apollo Server v4 to achieve type-safety?
    3 projects | /r/graphql | 19 Dec 2022
  • What do you think about nexus? I'm new at this and wondering if I should use it in my project.
    3 projects | /r/graphql | 19 May 2021
    There are multiple ways available of constructing a graphql schema. Usually, you can break down those into "SDL" First and "Code" First. A simple example of a Code First approach is the programmatic graphql.js API using `new GraphQLObjectType`. You define your schema with code. In an SDL First approach, you write your schema in the GraphQL SDL (as text) and define a resolver map. You can find some examples over here: https://graphql.org/graphql-js/constructing-types/ A lot of tooling has emerged of those two methods of building GraphQL schemas and you usually have to choose whether you wanna stick to Code First or SDL First. Tools like gqtx (https://github.com/sikanhe/gqtx), giraphql (https://github.com/hayes/giraphql), and nexus (https://github.com/graphql-nexus/nexus) are built around the Code First approach and improve the developer experience over the programmatic API form graphql.js by providing a more type-safe API when utilizing TypeScript. They ultimately all do the same, with slightly (more or less opinionated) different APIs. On the other hand tooling for SDL has also evolved. graphql-tools provides a more advanced interface over how you define the resolvers map and a lot of utilities for constructing your schema from SDL/resolver map partials distributed across different files (https://www.graphql-tools.com/docs/generate-schema/). Together, with graphql-codegen resolver type generation (https://www.graphql-code-generator.com/docs/plugins/typescript-resolvers) you can bring this to the next level if you are working with TypeScript and generate fully typed resolvers from the GraphQL SDL. You have to find out for yourself which approach is best suited for you. I have been using both on different projects and they both have benefits and trade-offs. My opinion is mostly based on the TypeScript developer experience. Code First seems to be the better pick for me if you have lots of computed fields that cannot be mapped 1:1 to the data sources, where you would have to add a lot of type resolver mappings configuration for codegen. With SDL I like that I have the feeling that I can write the schema faster and less clumsy, and the SDL is immediately readable. On Code First you, however, can still generate an SDL file from the coding schema. Maybe there is a niche open for an approach that combines Code and SDL First approaches. We will have to see what the future brings. Here are some more articles/threads regarding the topic: https://www.prisma.io/blog/the-problems-of-schema-first-graphql-development-x1mn4cb0tyl3 https://www.reddit.com/r/graphql/comments/fpkx7a/codefirst\_vs\_schemafirst\_development/ https://blog.logrocket.com/code-first-vs-schema-first-development-graphql/ Also, note that most GraphQL server/transports do or should not care about the way you construct your schema. E.g. the apollo-server docs show you only an SDL first way of constructing the schema (https://www.apollographql.com/docs/apollo-server/schema/schema/), but it is also possible to provide a schema instance(https://www.apollographql.com/docs/apollo-server/api/apollo-server/#schema). apollo-server defaults to advocating creating a schema with SDL (by using an old graphql-tools@4 version under the hood).
    3 projects | /r/webdev | 18 May 2021
    Tools like gqtx (https://github.com/sikanhe/gqtx), giraphql (https://github.com/hayes/giraphql), and nexus (https://github.com/graphql-nexus/nexus) are built around the Code First approach and improve the developer experience over the programmatic API form graphql.js by providing a more type-safe API when utilizing TypeScript. They ultimately all do the same, with slightly (more or less opinionated) different APIs.
  • Nexus and directive
    2 projects | /r/graphql | 29 Mar 2021
    If you want in-dept examples of plugins in nexusjs, I suggest that you have a look at how the default plugins are written here.

nexus-plugin-prisma

Posts with mentions or reviews of nexus-plugin-prisma. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-02-22.

What are some alternatives?

When comparing nexus and nexus-plugin-prisma you can also consider the following projects:

pothos - Pothos GraphQL is library for creating GraphQL schemas in typescript using a strongly typed code first approach

graphql-code-generator - A tool for generating code based on a GraphQL schema and GraphQL operations (query/mutation/subscription), with flexible support for custom plugins.

TypeGraphQL - Create GraphQL schema and resolvers with TypeScript, using classes and decorators!

typegraphql-prisma - Prisma generator to emit TypeGraphQL types and CRUD resolvers from your Prisma schema

nexus-prisma - Prisma plugin for Nexus

next-graphql-admin - Admin panel built with NextJS(Typescript), Material UI, Apollo Client & GraphQL. In the backend, Prisma 2 with Nexus and Mysql is used.

gqtx - Code-first Typescript GraphQL Server without codegen or metaprogramming

next-auth - Authentication for the Web.

FaunaCRUD - Tiny CRUD model for FaunaDB

e2e-type-safe-app - End-to-end type-safety demo with NextJs, GraphQL, Nexus and Prisma

nexus-shield - 🛡 Nexus plugin to ease the creation of the authorization layer