fullstack-starterkit VS graphql-code-generator

I'm learning fullstack JavaScript development, and was trying to get ideas for project organization going forward. I've already started putting the frontend/backend in separate subdirectories in monorepos to allow them to be developed independently, and it seems to be working well. However, this repo (https://github.com/karanpratapsingh/fullstack-starterkit) separates the two, but includes a third package.json in the root directory. What's the point of this? I've had experiences where package versions clash due to differences between package.json files in parent and child directories, is there a way to make sure this is avoided if I copy this organization?

Github: https://github.com/karanpratapsingh/fullstack-starterkit/tree/master/backend-go

Backend is now available in Go! 🥳

Hi, An opensource graphql first boilerplate https://github.com/karanpratapsingh/fullstack-starterkit might help

Full changelog Github

I usually set it up at root level, example that might help: https://github.com/karanpratapsingh/fullstack-starterkit

Full changelog/PR is available here

Full changelog/PR is available here

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.

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.

See https://github.com/dotansimha/graphql-code-generator with @graphql-codegen/typescript-graphql-request plugin

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.

It is already incoming, with an example in the repository. 😇 https://github.com/dotansimha/graphql-code-generator/pull/8863

The actual package is @ graphql-codegen/cli

GraphQL Codegen generates frontend types and React hooks from our GraphQL request definitions.

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.

For querying in React make sure you use GraphQL code generator https://www.the-guild.dev/graphql/codegen