Update auth.ts to await params
in NextJS 15
#1777
Open
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,
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:
📎 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.