Add support for graphql 14.x

[vicary]

Note: If your issue/feature-request/question is regarding the AWS AppSync service, please log it in the official AWS AppSync forum

Do you want to request a feature or report a bug? A suggested upgrade. More of a feature than a bug.

What is the current behavior? One of the requirements [email protected] is a product of 2018, a peer dependency there ^0.11.0 conflicts with many packages. Many NPM packages which directly or indirectly depends on graphql has advanced to at least add support for the first stable version 14.x.

I suggest a minor version upgrade to apollo-link-http@^1.5.0 for a better support to the community.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. N/A

What is the expected behavior? N/A

Which versions and which environment (browser, react-native, nodejs) / OS are affected by this issue? Did this work in previous versions? N/A

[vicary]

Taking reference from https://github.com/awslabs/aws-mobile-appsync-sdk-js/issues/436#issuecomment-518605638, a workaround at the moment is to add resolutions in package.json to force a minor version upgrade to the underlying dependency of apollo-link-http@^1.3.x.

"resolutions": {
  "apollo-link-http": "^1.5.0"
}

Credits to @beezeebly

[pickfire]

It should be graphql 15.x since it just released.

[vicary]

@pickfire TBH since they spun-off auth link and subscription handshake link I guess we kind of have to to wimp up our own offline mutation queue ourselves.

Apollo query cache is already semi-offline.

[pickfire]

3.0 is already broken for me such that subscriptions does not work. It's so troublesome every time I need to upgrade graphql to latest to run codegen and downgrade it back to 0.11 just for angular to be able to build.

[PatrykMilewski]

There are many troubles with libraries, if you have more than one graphql version installed and aws-appsync is requesting really outdated one.