Upgrade GraphQL to 16

[brainkim]

Allows for graphql@16 to be used with Apollo Client.

Fixes:

• Conflicting peer dependency GraphQL 16 #8991

[brainkim]

Maybe we can use a type assertion, and see if that lets us not bump the filesize of the client.

[brainkim]

@CruseCtrl The tricky thing is trying to support multiple GraphQL versions. The types as enums don’t exist in GraphQL 15, so I’m trying to figure out a way to continue to support multiple version. I also created this issue on the GraphQL.js repository (graphql/graphql-js#3356)

[CruseCtrl]

Ah, I see. In that case I can't think of a better way to solve this than what you've already done

[benjamn]

@brainkim You are probably already aware of this, but I tried checking out this PR, running npm i && npm test (all pass), then npm i graphql@15.x && npm test. When I do that, I get many Kind-related errors trying to run the tests. Unless I'm missing something, this means we don't have a strategy (yet) for supporting graphql@15 and graphql@16 simultaneously (never mind graphql@14). Hoping you have some more ideas here!

Aside: mind rebasing after #9004 (just package.json conflicts)?

[brainkim]

@benjamn I’m trying to see if we can get this merged and not have to make as many changes:

graphql/graphql-js#3360

[hwillson]

Awesome - thanks @brainkim!