Update @graphql-tools/executor peer dependencies to exclude graphql v16 about graphql-tools HOT 2 CLOSED

Thank you for creating the issue!

Actually the idea behind this executor is to support defer/stream, and the new features from the next graphql-js releases with the schemas created by any graphql version.

The executor also accepts signal: AbortSignal which allows us to cancel the execution (used in a Yoga plugin)

I think instead of dropping a peer dependency which would introduce a breaking change, we can basically support the old way of resolving the types as I did in this PR;
#6280

Let me know what you think. And you can also check the alpha versions published by CI if you want to try it out before the patch release.

Here you can find it; #6279 (comment)

from graphql-tools.

Thanks @ardatan! Appreciate the quick fix.

from graphql-tools.