Support passing relative path for URL about graphql-request

[frederikhors]

It works if I use window.location.origin since I'm using it in browser only.

[jasonkuhrt]

I think being explicit here is less confusing and makes for a better API, because we can validate that a valid URL is passed catching more user errors.

Upon release, I'll try to remember to mention this breaking change!

[jasonkuhrt]

If it only happens after you bundle then I think it's an issue in your project. What is the value of n.url? And, what is supplying the global URL?

[frederikhors]

Is the same URL I use with version v7.0.0-next.12.

graphql-request version is the only thing I change.

[jasonkuhrt]

It might be a breaking change in graphql-request rather than a bug.

Does your target runtime (browser?) have a global URL class? What is the URL value? Have you manually run that value through the global URL class constructor?

[frederikhors]

browser?

Yes

Does your target runtime have a global URL class?

Nope, all default.

I'm using it like this with both versions:

export const client = new GraphQLClient("/graphql", {
	fetch: createPersistedQueryFetch(fetch) // from from https://github.com/jasonkuhrt/graphql-request/issues/269
});

[jasonkuhrt]

Interesting, /graphql is not a valid URL. You are relying on the browser supplying the current host URL prefix. This approach is only valid in browsers. I'm not sure this feature should be supported, but I'll consider it. Let me know what you think for your use-case.