nexus
graphql-code-generator
Our great sponsors
nexus | graphql-code-generator | |
---|---|---|
4 | 69 | |
3,371 | 10,605 | |
0.4% | - | |
1.1 | 9.3 | |
5 months ago | 5 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
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
- What to use with Apollo Server v4 to achieve type-safety?
-
What do you think about nexus? I'm new at this and wondering if I should use it in my project.
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).
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
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.
graphql-code-generator
-
Integrating GraphQL Codegen with Storyblok: Step-by-Step Guide
The @graphql-codegen library is a bridge between your GraphQL schema and the actual code you write. It automates the generation of boilerplate code, ensuring that your data fetching layer is always up to date with your content structure.
-
The complete GraphQL Scalar Guide
In typescript and typescript-resolvers plugin v4.0.1, we have reverted the default ID Scalar input type to string. Read the pull request for more details.
-
Looking4Library: A GraphQL client that has query methods on the generated types
See https://github.com/dotansimha/graphql-code-generator with @graphql-codegen/typescript-graphql-request plugin
-
graphql-code-generator VS gqless - a user suggested alternative
2 projects | 2 Jun 2023
-
Making GraphQL Codegen Work For You: GraphQL Integration with React and TypeScript
Graphql Codegen is a code generation library for GraphQL that enables developers to generate custom code. It provides us developers with the ability to generate type definitions, query builders, documentation, and more by analyzing our GraphQL schemas. This makes it easier and faster to build GraphQL applications and reduces the time spent coding.
-
help wanted: Typescript GraphQL Types Response
It is already incoming, with an example in the repository. 😇 https://github.com/dotansimha/graphql-code-generator/pull/8863
-
Why does this package.json script for graphql-codegen only work if the package is installed directly in the package.sjon, even if it already exists in node_modules?
The actual package is @ graphql-codegen/cli
-
Why we ditched GraphQL for tRPC
GraphQL Codegen generates frontend types and React hooks from our GraphQL request definitions.
-
A journey towards a type-safe GraphQL API server
There are two main approaches to keeping the types of the GraphQL schema and entities in business logic in sync. You can generate the schema based on your TypeScript code (e.g. TypeGraphQL), or you can generate types based on your schema (e.g. GraphQL Code Generator). We opted for the latter since it slotted right into our existing GraphQL server implementation using Apollo Server.
-
Move to Hasura/GraphQL for db
For querying in React make sure you use GraphQL code generator https://www.the-guild.dev/graphql/codegen
What are some alternatives?
pothos - Pothos GraphQL is library for creating GraphQL schemas in typescript using a strongly typed code first approach
contentful-typescript-codegen - Generate TypeScript interfaces from a Contentful environment
TypeGraphQL - Create GraphQL schema and resolvers with TypeScript, using classes and decorators!
nexus-prisma - Prisma plugin for Nexus
TypeORM - ORM for TypeScript and JavaScript. Supports MySQL, PostgreSQL, MariaDB, SQLite, MS SQL Server, Oracle, SAP Hana, WebSQL databases. Works in NodeJS, Browser, Ionic, Cordova and Electron platforms.
nexus-plugin-prisma - Deprecated
rtk-query-codegen
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.
lint-staged - 🚫💩 — Run linters on git staged files
gqtx - Code-first Typescript GraphQL Server without codegen or metaprogramming
graphql-codegen-relay-plugins - Use the power of the relay-compiler with every GraphQL project!