Update auth.ts to await params in NextJS 15
#1777
Open
+1
−1
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
In NextJS 15, `params` from routes is now a Promise which must be awaited. Direct access is deprecated and will be removed in future versions. This change is backwards compatible because awaiting on a non-promise returns back the value itself. Without this change we get the following warning: ``` In route /api/auth/[auth0] a param property was accessed directly with `params.auth0`. `params` is now a Promise and should be awaited before accessing properties of the underlying params object. In this version of Next.js direct access to param properties is still supported to facilitate migration but in a future version you will be required to await `params`. If this use is inside an async function await it. If this use is inside a synchronous function then convert the function to async or await it from outside this function and pass the result in. ``` See more details in vercel/next.js#68812
ammubhave
changed the title
params in preparation for nextjs 15params in NextJS 15
Seva98
reviewed
Oct 26, 2024
|
Tried this, now getting
Seemingly from 'appRouteHandlerFactory' Would be great to use Auth0 with Next 15! Exciting |
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 NextJS 15,
paramsfrom routes is now a Promise which must be awaited. Direct access is deprecated and will be removed in future versions.This change is backwards compatible because awaiting on a non-promise returns back the value itself.
Without this change we get the following warning:
📎 References
See more details in vercel/next.js#68812
🎯 Testing
Add the SDK in NextJS 15 stable and see that the warning is getting generated whenever the auth0 endpoints are hit.