You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue arises from a breaking change introduced in Next.js 15, which transitioned certain APIs to be asynchronous. according to Next.js release notes:
the server now requires awaiting request-specific data (such as params, headers, cookies, and searchParams) before using their properties.
Reproduction
`import { handleAuth } from "@auth0/nextjs-auth0";
export const GET = handleAuth();
`
Additional context
The text was updated successfully, but these errors were encountered:
If you are running NextJS 15, you can see what the documentation says to solve this problem (see the image)
TL,DR: You have to run this (I strongly recommend to take the time to read the documentation first, as not all cases are compatible, but fortunately for me, this solved the problem) $ npx @next/codemod@canary next-async-request-api .
Umm, i have read a docs about the issues. However in my case(as always) simple solution with npx command does not work. But i also CAN NOT access Auth0 - node code, which actually causes the issue. Like, ta hell i'm suppose to do, and why such issue even occurred in stable version of Next?
(No blames, i just feel how much time i gonna waste on that, to finally fix it)
Checklist
Description
This issue arises from a breaking change introduced in Next.js 15, which transitioned certain APIs to be asynchronous. according to Next.js release notes:
Reproduction
`import { handleAuth } from "@auth0/nextjs-auth0";
export const GET = handleAuth();
`
Additional context
The text was updated successfully, but these errors were encountered: