Jon Koops

Hmmm, I don't think this is stale. There is still some work to be done for proper React 18 support that I haven't gotten to (mostly dependencies).

Thanks @tlabaj!

Looks like the specification now [stipulates the following](https://github.com/graphql/graphql-over-http/blob/main/spec/GraphQLOverHTTP.md#accept) for the `Accept` header: > It is RECOMMENDED that a client set the `Accept` header to `application/graphql-response+json; charset=utf-8, application/json; charset=utf-8`. Considering this,...

This is out of scope for `graphql-request`, but there is nothing stopping you from loading these GraphQl files with another tool and then passing the result into `graphql-request`.

This should be fixed now that we're no longer polyfilling the Fetch API (see #597).

This is not an issue related to `graphql-request`, but rather to TypeScript. If you create an `enum` in TypesScript, the default values of its members will be a number: ```ts...

Closing this, as this is expected behavior. The data structure is supposed to match the query you provide.

I don't think we want to bloat the package with additional dependencies, the idea of `graphql-request` is that it's a minimal library for calling GraphQL APIs. That said, nothing prevents...

@justin-buenaventura could you put this into a dedicated repository as a [Minimal, Reproducible Example](https://stackoverflow.com/help/minimal-reproducible-example)? With so many plugins and code it's hard to tell where things are going wrong.

Hi @MikeMcC399, sorry for the late reply. We're in the processes of moving our repo around, so I will take a look and see if I can get things to...