[HUD] upgrade to nextjs 13 #5862
Draft
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 ↗︎
|
facebook-github-bot
added
the
CLA Signed
yangw-dev
force-pushed
the
upgradeNextJs13
branch
from
c12ed23
to
53c6709
Compare
clee2000
added a commit
that referenced
this pull request
Nov 8, 2024
Upgrading cuz I think it's a good idea to be on a more recent version. idk what the consequences will be Theres also next 15.something but that came out really recently and next-auth doesn't list it as a compatible version octokit types changed which is why webhookToDyanamo looks different. Functionality should be the same, mostly just type changes + casting, and we have tests after #5869 Cousin to #5862 but does both slightly less and slightly more
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.
A title element received an array with more than 1 element as children. In browsers title Elements can only have Text Nodes as children. If the children being rendered output more than a single text node in aggregate the browser will display markup and comments as text in the title and hydration will likely fail and fall back to client renderingneed to test the bot offline