Fix Cannot read properties of null (reading 'textContent') when __NEXT_DATA__ element is missing
#75512
+13
−3
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
remorses
changed the title
Cannot read properties of null (reading 'textContent') when __NEXT_DATA__ element is missing
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.
When using
getServerSidePropsand streaming it can happen that the Next.js framework script runs before the__NEXT_DATA__script, if that happens the page becomes unresponsive and an error is thrown:Cannot read properties of null (reading 'textContent')Fix #53423
Fix #41299
Fix #47377
Fix nibtime/next-safe-middleware#83
This PR waits for
__NEXT_DATA__to be available if it's missing, it does not add any latency in case NEXT_DATA is present which should be true for most cases