Hello

Please DM me

I m familiar with Next project development and deployment on Vercel env

have you redeploy after adding the variable?
btw, use CLIENT_EMAIL for api route

Why are you asking people to DM you for help?

?

I m not asking help.

I m not here to get help from anyone

yes I have done redeploys since adding the environment variables to Vercel. The route iteslf is in a route.js file in an api folder. Everything about it works fine when the actual values are in the file, but it's broken for some reason with the values in the .env

Thanks I'll message you

don’t know much about next, or vercel so prolly not much help but that’s really odd. this might be something competely different but i know you can link your vercel project to your dir and then generate a .env for development somehow

i can’t tell you how or what i just think this exists, prolly doesn’t help

@Yellowstripe scad no worries

I cannot get the variables from env to work either. The strange thing is that they work in local dev as if the env doesn't contain anything. Console logging the object returns an empty object and for specific variables 'undefined'.

@Golden paper wasp have you figured it out?

yes I did. I think it was that I forgot to prefix the environment variables with NEXT_PUBLIC in the api/route.js file as well

For me, it was an issue with calling the .env inside a client component... rookie mistake...