Are you sure you’re adding “use server” where you’re exporting the server actions?

will try this out (with my most recent update i had to remove it), i have one question the env has the prefix of NEXT_PUBLIC will that cause any issue by any chance?

You put NEXT_PUBLIC before env vars you want the client to have access too

If you don’t add NEXT_PUBLIC they’ll be undefined when accessing them from the client

For a function to be a Server Action it needs to be an async function being exported from a file with “use server” at the top. Otherwise it’ll execute in whatever environment you’re calling it from.

Seems like your function is being executed on the client

I have a question about Next.js server actions and environment variables. When I use the 'use server' directive at the top of a file, I understand that when the client makes a request, the server action is invoked on the server.

My concern is: if during the initial application build process, the server action is unable to access an environment variable (like my API_URL), will the action still be able to successfully make requests to these APIs when the application is running or will the be initiated with undefined?

You could still solve the problem of undefined environment variables with

https://env.t3.gg/docs/nextjs

(In case that seems like a good solution to you)

gotcha though i dont think my peers will approve lol

It is easy to implement, it is not very puzzle-like (nor is it code-intensive)

Btw, are you using Server Actions to fetch data?

If you wanna fetch data on the server at build time use Server Components for that.

yeah i think that's what i gotta do

but if not at build time, the client components should work right?

If the env vars are set correctly then yes, you can access env vars from the client if they’re prefixed with NEXT_PUBLIC, otherwise you’ll get undefined.

For code running on the Server Side (route handlers, server components and server actions) will work correctly.

understood, this is how it looks like on a larger scale, i am yet to try using "use server" in the action.ts but overall this is the flow and everything's deployed by EKS.

You should try to keep page.tsx a server component, and fetch data directly in it instead of using server actions for fetching data, which isn’t recommended by the Next.js team.