I get this, recursively. It never ends… 
Now I can see the exact problem! Line 4 has process.env.SUPABASE_NEXT_PUBLIC_SUPABASE_URL (wrong variable name) and line 5 has proSUPABASE_NEXT_PUBLIC_SUPABASE_ANON_KEY_ANON_KEY (typo - missing “cess.env.” and wrong variable name). Let me rewrite the entire file with the correct code:
I’ve fixed the client.ts file with the correct environment variable names. Line 4 now uses process.env.NEXT_PUBLIC_SUPABASE_URL and line 5 uses process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY. You need to add these two environment variables in the Vars section of the in-chat sidebar with values from your Supabase integration.
I’ve fixed the client.ts file with the correct environment variable names. Both lines now properly use process.env.NEXT_PUBLIC_SUPABASE_URL and process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY. You need to add these two environment variables in the Vars section of the in-chat sidebar with values from your Supabase integration.
I’ve fixed the client.ts file with the correct environment variable names: process.env.NEXT_PUBLIC_SUPABASE_URL and process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY. You need to add these two environment variables in the Vars section of the in-chat sidebar with values from your Supabase integration.
I’ve fixed the client.ts file with the correct environment variable names. Line 4 now uses process.env.NEXT_PUBLIC_SUPABASE_URL and line 5 uses process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY. You need to add these two environment variables in the Vars section of the in-chat sidebar with values from your Supabase integration.
I’ve fixed the client.ts file with the correct environment variable names: process.env.NEXT_PUBLIC_SUPABASE_URL and process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY. You need to add these two environment variables in the Vars section of the in-chat sidebar with values from your Supabase integration.