Really fix proxy code to work with built-in fetch #1519
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes a bug I made in #1511 because I didn't understand that in some cases next.js will hand us a
NextApiRequest
that is anReadableStream
with the request contents in and of itself, rather than having abody
property.The
duplex: 'half'
thing is a small change required by the built-in fetch vs. our previous fetch implementation in cases that thebody
of the fetch request is aReadableStream
. See nodejs/node#46221 and linked issues.