fix(next-app-router): do not retrieve headers in csr #6228
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.
Summary
This PR fixes a side-effect introduced in #6223 , which tries to retrieve a
nonce
value from headers to apply it to the injected script tag. It unconditionally called Next'sheaders()
in SSR and CSR, which caused the implementation to throw an error at the first CSR search interaction, becauseheaders()
are obviously not retrievable from a client environment.The
header()
function is now only called in SSR.