fix: resolve cloned response in parallel in fetchBaseQuery

[GU5TAF]

Fixes #1451

[netlify]

✔️ Deploy Preview for redux-starter-kit-docs ready!

🔨 Explore the source changes: 046d3c4

🔍 Inspect the deploy log: https://app.netlify.com/sites/redux-starter-kit-docs/deploys/612b81182d04a00007284e87

😎 Browse the preview: https://deploy-preview-1452--redux-starter-kit-docs.netlify.app

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 046d3c4:

Sandbox	Source
Vanilla	Configuration
Vanilla Typescript	Configuration
rsk-github-issues-example	Configuration
fetchBaseQuery broken with node-fetch	Issue #1451

[phryneas]

Thanks for the PR! This has already been solved over in #1277 (with be2dbb7 ), which also adds some other changes to fetchBaseQuery, so this change would probably result in a merge error and mostly be removed after merge of that PR.

So I'm gonna close this one, I hope that doesn't discourage you from future PRs.

Sorry you had to go down this rabbit hole. I know from personal experience how frustrating that bug is.

Until we release the next version, you can use the CodeSandbox build of this PR - it will stay around. Also, if you are in a SSR environment, feedback in #1277 would be great :)

[GU5TAF]

Ah, I skimmed that PR but missed that it had been addressed 🤦‍♂️ Happy to hear it's being fixed, it was indeed a frustrating evening of wondering why fetch wasn't working 😅

[phryneas]

Yeah, that cost me about two days I believe 😅