the offending function is

//login user
export const validateRequest = cache(
  async (): Promise<
    { user: User; session: Session } | { user: null; session: null }
  > => {
    const sessionId = cookies().get(lucia.sessionCookieName)?.value ?? null;
    if (!sessionId) {
      return {
        user: null,
        session: null,
      };
    }

    const result = await lucia.validateSession(sessionId);
    // next.js throws when you attempt to set cookie when rendering page
    try {
      if (result.session && result.session.fresh) {
        const sessionCookie = lucia.createSessionCookie(result.session.id);
        cookies().set(
          sessionCookie.name,
          sessionCookie.value,
          sessionCookie.attributes
        );
      }
      if (!result.session) {
        const sessionCookie = lucia.createBlankSessionCookie();
        cookies().set(
          sessionCookie.name,
          sessionCookie.value,
          sessionCookie.attributes
        );
      }
    } catch {}
    return result;
  }
);

I believe the import cookies is causing it

│ import { cookies } from "next/headers";

where do you use validateRequest?

in a client component?

yes its supposed to be used in server components only but i made a custom hook calling

validateRequest

and imported it to my client . idk if i did that properly though

this is not going to work
1. cookies() cannot be used in client component
2. cookies().set() doesn't work in page component

you should handle it in middleware

but since you are using prisma, it may not work in middleware

im trying to call

validateRequest

to authenticate my users session so i can display the user to the client component, is there any workaround to this

how do you call validateRequest now?

import { validateRequest } from "../actions/auth";

const getUser = async () => {
    const { user } = await validateRequest();
    return user;
}

export default getUser;

I just import this function to my client component

oh making getUser a server action seemed to have solved it? im not sure why though

yes

what changed though? i thought the code was still all being executed on the server before. im still new to nextjs13

you mark it as a server action

so it can be executed on client

oh gotcha so before the code could only run on

the server

yes