GraphiQL.createFetcher does not work for subscriptions-transport-ws

As shown in this PR on express-graphql: https://github.com/graphql/express-graphql/pull/739/files#diff-f851f2ce2fbcb0220aaca183def93d7ced5b533fead2016551cfd6d37b357ae5, I started the graphql server with subscription using legacy subscriptions-transport-ws.

Then on the client side I create fetcher like this:

window.GraphiQL.createFetcher({url: fetchURL, subscriptionUrl: ${safeSerialize(
            subscriptionEndpoint,
          )}});

Then I got error as shown in the below screenshot:

The same client side code works if I started a graphql server using graphql-ws though: https://github.com/graphql/express-graphql/pull/739/files#diff-4f5f57981087dfef3de9e960e86656c7a1d1ef9f424fd0a75e32751163a286e1

[acao]

@junminstorage introduced the legacyClient option as requested in the above PR, and just made it so that only graphql-ws is tried with subscriptionsUrl since the failover logic is too complex and unnecessary, when most projects are instantiating a custom client instance anyways.

thanks for all your work @junminstorage getting this working in the ecosystem, hoping to help you get everything working nicely here and in express-graphql in the following weeks!

[junminstorage]

@acao make sense. thank you!