Should we match the default variables to what works with Supabase and Vercel?

[hdwebpros]

My headache when using Supabase branching and Vercel with this module

This module uses SUPABASE_KEY and SUPABASE_SERVICE_KEY. The issue is that when you enable the Vercel integration on Supabase, Supabase populates SUPABASE_ANON_KEY and SUPABASE_SERVICE_ROLE_KEY. I was tripped up on this for a bit.

How to tackle this

I considered changing my .env vars to match what Supabase was outputting. It would be even simpler if the module suggested to use the naming structure that Supabase apparently uses and suggests.

[Matthewenderle]

I do agree that this can be a little annoying. I just got caught up on this because I pushed my SUPABASE_KEY_DEV to my coolify and it was not happy.

It would be nice if it had the env it is looking for inline

# instead of 
[warn] [@nuxt/supabase] Missing supabase url, set it either in `nuxt.config.js` or via env variable

# have it inline
[warn] [@nuxt/supabase] Missing supabase anon key, set it either in `nuxt.config.js` or via env variable (SUPABASE_KEY)