temp-fix: rendering error in next.js 14.0.2 caused by next.js bug #534
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.
vercel/next.js#57815 introduced a critical bug for us that breaks rendering due to the assumption that their internal request shape is always
NodeNextRequest
(and should have theoriginalRequest
property on it), and is neverWebNextRequest
(which doesn't have theoriginalRequest
property).This fix is intended to be a temporary band-aid until the issue is fixed in Next.js. I raised an issue at vercel/next.js#58265.