tql VS graphql-request

Can we do projects that we think will stay at $0 but we still hope might gain traction?

OSS: typed-graphql-builder https://typed-graphql-builder.spion.dev/ is a TypeScript based graphql query builder.

It was inspired by tql (https://tql.dev/) but generates a much smaller client and has full, automatic type inference for query variables used in input objects.

The aws-sigv4-fetch package can be integrated into GraphQL libraries like graphql-request. For example, you can pass the signedFetch function as the custom fetch option:

For Next.js projects, one of the options can be the typescript-graphql-request plugin. Under the hood this plugin works with the graphql-request library — a minimal, flexible, and easy-to-use GraphQL client. With typescript-graphql-request, we generate an SDK that is fully typed and allowing us to make strongly-typed GraphQL requests. This nicely integrates with data fetching in Next.js Server Components, enabling us to pre-render pages with data from Storyblok.

but i don't want to use that external library

An example of a Snowflake API request using JavaScript. This example uses the graphql-request library to issue the actual GraphQL request. Install the dependency:

I mentioned already we can use just about any client want when fetching GraphQL data. Prisma's graphql-request is a simple and lightweight option, and that is what I’ve used here.

To do this, you will make use of a tool called GraphQL Codegen to generate TypeScript types based on the GraphQL schema Sanity provides. You will then use graphql-request to actually fetch the data.

What about https://github.com/prisma-labs/graphql-request that has 4.8k starts / 254 forks?

If you don't want to use Apollo, I suggest using codegen + graphql-request. There is a codegen plugin for graphql-request that auto generates a typesafe client sdk with all your queries as methods on the graphql-request client. Super clean and lightweight. https://github.com/prisma-labs/graphql-request