graphql-utils VS nodejs-api-starter

This is what I meant you should be doing anyway. Dataloader or simple field resolvers are extremely inefficient. You can use a library I created - GraphQL-Utils - to retrieve a mapping of the fields you need to JOIN and then do so with your ORM or data mapping technology of choice (Prisma, Knex.js, etc.)

By the way, I see you're using Docusaurus, something that might be kind of cool to integrate is a live GraphQL playground with some mock data if you want to spruce it up. I have a documentation for my own library, GraphQL-Utils that does this. Might be worth checking out the source code for my Sandbox component!

If you would like to see how I've gone about implementing it so far, I opened a new branch, keymap, in the GraphQL-Utils GitHub repository and if you happen to have any input on those problems I mentioned I'd really appreciate it!

I released a library, GraphQL-Utils, which contains helpers such as resolveSelections(), as well as a full NestJS integration that ships with decorators like @Selections(), which you can see above. It supports wildcards to retrieve fields that contain subselections, flat fields, deep fields, and many more options!

GitHub - Jenyus-Org/graphql-utils: Utilities and helpers to make working with GraphQL.js based APIs simpler.

I come from C# and Java so the structure just makes so much more sense and the tooling is way better. I also love the GraphQL integration and made a library to optimize queries, so yeah, I'm stuck in the ecosystem.

Check out my blog post on GraphQL-Utils if you use NestJS for GraphQL projects!

NestJS is amazing. I've been spending a lot of time with it and using its GraphQL integration to build hybrid APIs. I like it so much that I spent some time figuring out how to optimize query relations and wrote a package to aid in doing so called GraphQL-Utils.

(1) React + API monorepo VS (2) React + API as separate repositories

Nope. Just plain GraphQL.js + Knex.js (example), often typed manually since it's not where most of the time spend on when building an API server (though it can be automated via a scaffolding script if there are too many db tables). Generating TypeScript definitions off the actual db schema using knex-types (example).

Examples: - https://github.com/kriasoft/node-starter-kit - basic Node.js API starter kit - https://github.com/kriasoft/graphql-starter - monorepo template with GraphQL, React, Relay

https://github.com/kriasoft/graphql-starter - See web/relay.config.js, run: yarn relay

Your first example is the code-first development approach (example), while the latter one is schema-first, popularized by Apollo.

Source code (example): https://github.com/kriasoft/graphql-starter

Here is yet another example of a Node.js (Express) middleware that encodes/decodes JWT (OAuth) token into a session cookie: https://github.com/kriasoft/graphql-starter/blob/main/api/session.ts

Details: It's going to be a Reddit-like community but for books. Just started working on this idea last week (solo) by branching out from graphql-starter open source template. Looking for feedback and feature requests.

Yes, for example: