feat(core): Add support for graphql.js’ built-in TypedQueryDocumentNode

[kitten]

Summary

graphql.js now has a built-in type for typed DocumentNodes, which we must adopt to support tools that rely on this type instead of @graphql-typed-document-node/core.

We can maintain our prior approach of having a copied type to maintain backwards- and forwards- compatibility by extending our own type with the type property carrying the types we need. The only difference to the other package is that graphql.js uses a different name for the property: https://github.com/graphql/graphql-js/blob/e171a14/src/utilities/typedQueryDocumentNode.ts#L8-L22

This has been tested with the following ts file:

import { Client, TypedDocumentNode } from '@urql/core';
import type { TypedQueryDocumentNode } from 'graphql';
import type { TypedDocumentNode as LegacyTypedDocumentNode } from '@graphql-typed-document-node/core';

type Exact<T extends { [key: string]: unknown }> = { [K in keyof T]: T[K] };
type Variables = Exact<{ [key: string]: never; }>;

const client = new Client({ url: 'test', exchanges: [] });

const x: TypedQueryDocumentNode<{ data: { hello: 'world' } }, Variables> = {} as any;
const y: LegacyTypedDocumentNode<{ data: { hello: 'world' } }, Variables> = {} as any;
const z: TypedDocumentNode<{ data: { hello: 'world' } }, Variables> = {} as any;

const { data: xData } = client.readQuery(x, {})!;
const { data: yData } = client.readQuery(y, {})!;
const { data: zData } = client.readQuery(z, {})!;

let test = xData;
test = yData;
test = zData;

Set of changes

• Add __ensureTypesOfVariablesAndResultMatching property to TypedDocumentNode