In previous versions, it was possible to use a relative httpEndpoint url.
In development, this could get redirected using the nitro proxy.
With the newest release, I now get the error Failed to parse URL from /api/graphql
Expected behaviour
A relative url should also be a viable input for the httpEndpoint property
500
Failed to parse URL from /api/graphql
at C:\Users\niwi\Desktop\Repos\Personal\Atlas\node_modules\@apollo\client\core\QueryManager.js:679:19
at both (C:\Users\niwi\Desktop\Repos\Personal\Atlas\node_modules\@apollo\client\utilities\observables\asyncMap.js:17:53)
at C:\Users\niwi\Desktop\Repos\Personal\Atlas\node_modules\@apollo\client\utilities\observables\asyncMap.js:10:72
at new Promise ()
at Object.then (C:\Users\niwi\Desktop\Repos\Personal\Atlas\node_modules\@apollo\client\utilities\observables\asyncMap.js:10:24)
at Object.error (C:\Users\niwi\Desktop\Repos\Personal\Atlas\node_modules\@apollo\client\utilities\observables\asyncMap.js:18:49)
at notifySubscription (C:\Users\niwi\Desktop\Repos\Personal\Atlas\node_modules\zen-observable\lib\Observable.js:140:18)
at onNotify (C:\Users\niwi\Desktop\Repos\Personal\Atlas\node_modules\zen-observable\lib\Observable.js:179:3)
at SubscriptionObserver.error (C:\Users\niwi\Desktop\Repos\Personal\Atlas\node_modules\zen-observable\lib\Observable.js:240:7)
Environment
Describe the bug
In previous versions, it was possible to use a relative httpEndpoint url. In development, this could get redirected using the nitro proxy. With the newest release, I now get the error
Failed to parse URL from /api/graphql
Expected behaviour
A relative url should also be a viable input for the
httpEndpoint
propertyReproduction
apollo.config.ts
next.config.ts
Additional context
No response
Logs