Replace subscriptions-transport-ws with graphql-ws

[alaycock]

The project subscriptions-transport-ws is no longer being maintained. Based on its README graphql-ws is the recommended alternative. It would be worthwhile to exploring if graphql-ws can be integrated as-is or if changes are required, updating the sample application to use graphql-ws, and updating the documentation to facilitate that new library.

[michalkvasnicak]

I'm sorry it took so long. I don't have time at the moment to try this so if you are able to spend some time on investigating this I'd appreciate this, otherwise it'll have to wait until I have some free capacity to do this.

[mathenshall]

At Nurx (www.nurx.com), we are heavily investing in using this package and are willing to take the lead in adding support for graphql-ws. Is there anybody else in the community who would be willing to help review, and test/evaluate?

[CaerusKaru]

@mathenshall More than happy to review, test, and evaluate any work you submit

[medv]

At Nurx (www.nurx.com), we are heavily investing in using this package and are willing to take the lead in adding support for graphql-ws. Is there anybody else in the community who would be willing to help review, and test/evaluate?

Did you end up transitioning to graphql-ws, if so how did it go?

[ashramsey]

Hi all, I have a fork (my first ever, so be kind) that has apollo v3 and graphql-ws. Its a first pass, have the example apps and tests passing. Some bits I need to circle back around to, but would love to compare notes if anyone is interested.

(EDIT) Of note, I was unsure of the use of createGraphQLServerOptions.