You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
node-fetch causes a socket-hang-up bug on node19 and higher and is described extensively here node-fetch/node-fetch#1735.
I ran into this exactly on our node server that creates seed data on localhost using batched API calls using graphql-request.
I don't know the inner workings of graphql-request but I would have thought this requires an upgrade of currently used node-fetch package since bug has been fixed there?
Reproduction Steps/Repo Link
There is nothing out of the ordinary here, just std. use of graphql-request which has worked perfectly for 3 years until my node version was upgraded.
The text was updated successfully, but these errors were encountered:
We experienced the same issue. By default, this package uses cross-fetch, unless another fetch function is specified. You can use your own GraphQLClient instance with your desired fetch, e.g. node's native fetch, which does not have this issue.
We experienced the same issue. By default, this package uses cross-fetch, unless another fetch function is specified. You can use your own GraphQLClient instance with your desired fetch, e.g. node's native fetch, which does not have this issue.
According to #597 this issue should be fixed since cross-fetch has been removed, but somehow I still encounter it in version 6.1.0 and could only fix by specifying fetch manually as above, did I miss something ?
Screenshot
n/a
Description
node-fetch
causes a socket-hang-up bug on node19 and higher and is described extensively here node-fetch/node-fetch#1735.I ran into this exactly on our node server that creates seed data on localhost using batched API calls using graphql-request.
I don't know the inner workings of graphql-request but I would have thought this requires an upgrade of currently used node-fetch package since bug has been fixed there?
Reproduction Steps/Repo Link
There is nothing out of the ordinary here, just std. use of graphql-request which has worked perfectly for 3 years until my node version was upgraded.
The text was updated successfully, but these errors were encountered: