Fix request check in node 16 #1250
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
ewanharris
approved these changes
Jun 13, 2023
Widcket
reviewed
Jun 13, 2023
| expect(isRequest(req)).toBe(true); | ||
| expect(isRequest(reqNode16)).toBe(true); | ||
| expect(isRequest(reqNext)).toBe(true); | ||
| expect(isRequest(nodeReq)).toBe(false); |
There was a problem hiding this comment.
Should this include expect(isRequest(nextApiReq)).toBe(false);?
There was a problem hiding this comment.
Sure - let me add that too
adamjmcgrath
commented
Jun 13, 2023
Widcket
approved these changes
Jun 13, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
📋 Changes
Requestis a Proxy toRequestin Node 16 on development server in Next.js. Fallback to checkingreq.headersin these instances.📎 References
fixes: #1246