-
-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Response
is not defined in Node
#265
Comments
Response
is not defined in SSR contextsResponse
is not defined in Node
I will take a look as soon as possible! Bare with me! |
Any movement on this? 🙏 |
Experiencing the same issue with Gatsby static build render (on server). Are there any updates on this by chance? |
Ended up switching to https://react-query.tanstack.com/ - would recommend it! |
@piersolenski thanks for the reference! |
Sorry for the delay guys. I'm extremely busy and haven't had time to debug this. A PR is very much welcomed. |
I am getting same error after upgrading Gatsby from 2 to 4. |
Describe the bug
useFetch
crashes the SSR server if the code makes any call to the getter for aresponse
. The getter usesinstanceof Response
, expectingReponse
on the global namespace, which is undefined in Node.To Reproduce
Steps to reproduce the behavior:
useFetch
Expected behavior
The getter for responses should return the right value whether on the server or on the client.
The text was updated successfully, but these errors were encountered: