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
Just had this issue when I got the latest graphql-request and it was hard to track down. After finding similar issues it seems to be that graphql-request is now using isomophic-fetch which in a react native build fails:
It also looks like that the libarary is not well supported. It was last published 2 years ago and a number of PRs are outstanding... even one that resolves this issue.
Not sure if it would be a solution to move away from this libarary but in its current for I cannot use this within my app.
The text was updated successfully, but these errors were encountered:
Thanks a lot for raising this issue @aqwert. Given that most browsers seem to natively support fetch by now and node-fetch seems to be actively maintained, we could switch over to node-fetch instead. Would that work in your case?
Just had this issue when I got the latest graphql-request and it was hard to track down. After finding similar issues it seems to be that
graphql-request
is now using isomophic-fetch which in a react native build fails:Can't find variable: self
http://imgur.com/PzHkGC6
Issues reported:
It also looks like that the libarary is not well supported. It was last published 2 years ago and a number of PRs are outstanding... even one that resolves this issue.
Not sure if it would be a solution to move away from this libarary but in its current for I cannot use this within my app.
The text was updated successfully, but these errors were encountered: