I’m experiencing a frustrating issue across my entire v0 account when trying to configure Supabase. It seems that every time I try to spin up a project all the ENV variables that get loaded into to my v0 chat are prefixed with SUPABASE_ including NEXT_PUBLIC variables. The end result is every Supabase project fails to initialize properly and doesn’t work.
Here is an example of the project ENV variables:
SUPABASE_POSTGRES_URL=“************”
SUPABASE_POSTGRES_PRISMA_URL=“*******************”
SUPABASE_SUPABASE_URL=“************”
SUPABASE_NEXT_PUBLIC_SUPABASE_URL=“************************”
SUPABASE_POSTGRES_URL_NON_POOLING=“************************”
SUPABASE_SUPABASE_JWT_SECRET=“*******************”
SUPABASE_POSTGRES_USER=“*************”
SUPABASE_NEXT_PUBLIC_SUPABASE_ANON_KEY=“*****************************”
SUPABASE_POSTGRES_PASSWORD=“*****************”
SUPABASE_POSTGRES_DATABASE=“*****************”
SUPABASE_SUPABASE_SERVICE_ROLE_KEY=“*************************”
SUPABASE_POSTGRES_HOST=“*************”
SUPABASE_NEXT_PUBLIC_SUPABASE_ANON_KEY=“*****************”
This seems like a new issue as I have 2 previous projects that we’re initialized within a v0 chat and worked flawlessly. I feel like I’m missing something painfully obvious here but I have reviewed every setting I can find with no luck. To show the difference here are the ENV variable names from a project I initialized ~3 weeks ago:
POSTGRES_URL=“************”
POSTGRES_PRISMA_URL=“*******************”
SUPABASE_URL=“************”
NEXT_PUBLIC_SUPABASE_URL=“************************”
POSTGRES_URL_NON_POOLING=“************************”
SUPABASE_JWT_SECRET=“*******************”
POSTGRES_USER=“*************”
NEXT_PUBLIC_SUPABASE_ANON_KEY=“*****************************”
POSTGRES_PASSWORD=“*****************”
POSTGRES_DATABASE=“*****************”
SUPABASE_SERVICE_ROLE_KEY=“*************************”
POSTGRES_HOST=“*************”
NEXT_PUBLIC_SUPABASE_ANON_KEY=“*****************”
Any help/ guidance would be incredibly appreciated!