Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fetchBaseQuery does not work with node-fetch due to usage of response.clone() #1451

Closed
GU5TAF opened this issue Aug 29, 2021 · 1 comment
Closed

fetchBaseQuery does not work with node-fetch due to usage of response.clone() #1451

GU5TAF opened this issue Aug 29, 2021 · 1 comment

Comments

@GU5TAF
Copy link

GU5TAF commented Aug 29, 2021

When fetchBaseQuery is used in a node environment where fetch has been poly/ponyfilled requests fail to complete due the usage of response.clone(). This is a known issue with node-fetch#custom-highwatermark and is solved by resolving the cloned response in parallel.

Minimal Repro
@GU5TAF GU5TAF mentioned this issue Aug 29, 2021
Closed
@GU5TAF
Copy link
Author

GU5TAF commented Aug 29, 2021

Closing due to issue being addressed in #1277

@GU5TAF GU5TAF closed this as completed Aug 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: resolve cloned response in parallel in fetchBaseQuery GU5TAF/redux-toolkit
1 participant
@GU5TAF