graphql-let VS graphql-zeus

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.

When I asked this in StackOverflow over a year ago I reached the solution of using graphql + graphql-zeus.

You can think of GraphQL Zeus as Prisma for the frontend: it writes GraphQL queries out of JavaScript objects and produces the proper return types.

graphql-zeus: You write your graphql queries using a JavaScript object like syntax. Looks cool, but I think it's too big of a burden on the team to have to give up writing queries using graphql-tag/gql.

https://github.com/graphql-editor/graphql-zeus generates subscription code and in generated code you'll find simple apiSubscription function you can use/copy

You can do this with GraphQL too:

https://genql.vercel.app/

https://github.com/graphql-editor/graphql-zeus

I did a 5 min talk about these newer breeds of codegen tools (where it's a single client SDK that does automatic return type inference based on the input args), it's really neat:

https://www.youtube.com/watch?v=7n3MeMFHiMk