Skip to content

23 tools · 109 fixes · 30 issue guides · Sources: Supabase, GitHub, OWASP, Vercel + 30

v0

Public env vars, the Supabase anon key, and row level security in v0

By ShipSecurely Editorial · Updated · How we make these guides

high

On a v0 project that uses Next.js, the public prefix is NEXT_PUBLIC_ , not VITE_ . Keep the project URL and publishable key in NEXT_PUBLIC_ names.

Fix for v0

On a v0 project that uses Next.js, the public prefix is NEXT_PUBLIC_, not VITE_. Keep the project URL and publishable key in NEXT_PUBLIC_ names. Keep the secret key in a server module that client components do not import, under a name without that prefix. Build again after you change the variable, because Next.js inlines NEXT_PUBLIC_ at next build.

The five-minute check, the other platforms, and the agent prompt are on the full guide. More v0 fixes are on the v0 page.