We have recently upgraded to the latest version (4.X) of the graphql-request package. Additionally, we are utilizing an older version of GraphQL Yoga v2.
During this process, we encountered a type conflict error. This was due to an older version of @whatwg-node/fetch that declared the same global as this package.
Fortunately, we noticed that in the newer version of @whatwg-node/fetch, they have removed the global declaration. This change helps avoid conflicts with this library. However, I'm wondering if it might be a good idea for this library to also remove the global declaration to prevent potential conflicts with other libraries.
Hello,
We have recently upgraded to the latest version (4.X) of the graphql-request package. Additionally, we are utilizing an older version of GraphQL Yoga v2.
During this process, we encountered a type conflict error. This was due to an older version of @whatwg-node/fetch that declared the same global as this package.
Fortunately, we noticed that in the newer version of @whatwg-node/fetch, they have removed the global declaration. This change helps avoid conflicts with this library. However, I'm wondering if it might be a good idea for this library to also remove the global declaration to prevent potential conflicts with other libraries.