milllianlmx/tabatago
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: support both EXPO_PUBLIC and NEXT_PUBLIC env vars

Browse Source 
- Update Supabase client to check for both naming conventions
- Fixes connection issue when using Expo env vars in Next.js app
This commit is contained in:
Millian Lamiaux
2026-03-17 10:14:32 +01:00
parent 66a211ce8b
commit 4c5bcc41c5
1 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
admin-web/lib/supabase.ts
View File

@@ -1,11 +1,17 @@
import { createClient } from '@supabase/supabase-js'
const supabaseUrl = process.env.NEXT_PUBLIC_SUPABASE_URL || 'http://localhost:54321'
const supabaseKey = process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY || 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24iLCJleHAiOjE5ODM4MTI5OTZ9.CRXP1A7WOeoJeXxjNni43kdQwgnWNReilDMblYTn_I0'
// Support both EXPO_PUBLIC_ (mobile) and NEXT_PUBLIC_ (web) prefixes
const supabaseUrl = process.env.NEXT_PUBLIC_SUPABASE_URL
|| process.env.EXPO_PUBLIC_SUPABASE_URL
|| 'http://localhost:54321'
const supabaseKey = process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY
|| process.env.EXPO_PUBLIC_SUPABASE_ANON_KEY
|| 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24iLCJleHAiOjE5ODM4MTI5OTZ9.CRXP1A7WOeoJeXxjNni43kdQwgnWNReilDMblYTn_I0'
if (typeof window !== 'undefined') {
console.log('Supabase URL:', supabaseUrl)
console.log('Supabase Key configured:', !!supabaseKey)
console.log('Using EXPO_PUBLIC:', !!process.env.EXPO_PUBLIC_SUPABASE_URL)
console.log('Using NEXT_PUBLIC:', !!process.env.NEXT_PUBLIC_SUPABASE_URL)
}
export const supabase = createClient(supabaseUrl, supabaseKey, {