nodejs-api-starter VS graphql-let

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

I personally enjoy using GraphQL.js as an ORM in combination with Knex.js - starting with database design, using Knex migrations, then generating GraphQL types (models) either automatically or manually, which then are being assembled into a single unified API endpoint.

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

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

Yes, for example:

Under the hood, @lente/vite-plugin-graphql uses graphql-let, and .graphql-let.yml is where we define where the GraphQL schema is located and how to identify the GraphQL files to be parsed. Check out this repo for more details on the options available https://github.com/piglovesyou/graphql-let.

graphql-let is a wrapper tool that makes using GraphQL Code Generator smoother and easier. In this article, I'll explain what graphql-let is and how it relates to GraphQL Code Generator.

I think all the tools you and /u/catterpillars_dreams need are there. You just need a combination of graphql-code-generator, ESLint, and editor plugins. Maybe you could contribute to the graphql-let project, which attempts to make it easier to set everything up.