feat(nextjs): Support new async APIs (headers(), params, searchParams)
#13828
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
lforst
changed the title
headers(), params, searchParams)
chargome
approved these changes
Sep 30, 2024
This was referenced Oct 2, 2024
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.
Changes in Next.js vercel/next.js#68812
This PR is mostly just adjusting our E2E tests so they don't fail while building.
Additionally, we had to update the
withServerActionInstrumentationAPI in a semver-minor way so you can pass a promise to theheadersoption. TheReadonlyHeaderstype isn't exposed in all Next.js versions so for now I typed it asany.Resolves #13805
Resolves #13779
Resolves #13780