I can manage client-side sessions using useSession from Auth.js (NextAuth v5) with Next.js and TypeScript. However, the return type of useSession includes a “loading” state, and the session is null, even when specifying the required: true option.

I can manage client-side sessions using useSession from Auth.js (NextAuth v5) with Next.js and TypeScript. However, the return type of useSession includes a “loading” state, and the session is null, even when specifying the required: true option.

I can manage client-side sessions using useSession from Auth.js (NextAuth v5) with Next.js and TypeScript. However, the return type of useSession includes a “loading” state, and the session is null, even when specifying the required: true option.

I can manage client-side sessions using useSession from Auth.js (NextAuth v5) with Next.js and TypeScript. However, the return type of useSession includes a “loading” state, and the session is null, even when specifying the required: true option.

I can manage client-side sessions using useSession from Auth.js (NextAuth v5) with Next.js and TypeScript. However, the return type of useSession includes a “loading” state, and the session is null, even when specifying the required: true option.

I can manage client-side sessions using useSession from Auth.js (NextAuth v5) with Next.js and TypeScript. However, the return type of useSession includes a “loading” state, and the session is null, even when specifying the required: true option.

Okay so I was working with NextJs implementing NextAuth for a page that’s supposed to be accessed by admin only. Then, I was introduced to the new concept of the “middleware.ts” file, which apparently should execute a function for every determined route.
But it is not working for me for some reason, check this out, I removed everything, and only kept a small console log just to know if the file is running, but it doesn’t seem to log anything to the browser inspect or the terminal.

I’ve been working on extending the session in authjs v5 using callbacks to implement role-based authorization. I aim to assign a role to the token generated and then pass it to the session. The role is defined in the User Model in Prisma Schema as an enum with values user or admin.
Here is the relevant code from my auth.ts file:

I have this error and I can’t find any solution on the Internet.

I have a problem with adding additional values to SESSION, I tried to do it according to the documentation but nothing gave the expected result I always get 3 same values (user, email, image). I would like these 3