fix(next): conditional RSC support #5745
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
|
balazsorban44
changed the title
|
🎉 Experimental release published 📦️ on npm! pnpm add next-auth@0.0.0-pr.5745.7387139fyarn add next-auth@0.0.0-pr.5745.7387139fnpm i next-auth@0.0.0-pr.5745.7387139f |
mmartinsoliv
approved these changes
Nov 6, 2022
samuelsd1
reviewed
Nov 6, 2022
ThangHuuVu
approved these changes
Nov 7, 2022
|
Still the same error on 4.18.7 |
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.
Fixes #5743
We accidentally broke Next.js 12 support via #5741 which has an import to
next/headersthat only exists in Next.js 13. This PR wraps the import into a conditional to prevent the error from happening in Next.js 12 apps.☕️ Reasoning
🧢 Checklist
🎫 Affected issues
Please scout and link issues that might be solved by this PR.
Fixes: INSERT_ISSUE_LINK_HERE
📌 Resources