Not possible to catch the error when fetching schema

[rchl]

The graphql-language-service-cli package (from a project hosted at https://github.com/graphql/graphiql) uses this package to load graphql settings and I've recently reported an issue in it that when the graphql server is not running, there is an unhandled promise rejection reported in the console. That issue is here: graphql/graphiql#1711.

It turns out that the consumer of this graphql-config package can't do anything to prevent that unhandled rejection (and unhandled rejections are bad as they crash the process from Node 14 (I believe)).

The consumer should be able to catch the error that triggers on connecting to the graphql server or the graphql-config package should catch it and somehow propagate the error to the caller.

This error happens when calling loadConfig when the graphql server is not running so connecting to it will fail.