Errant warnings when configuring with NUXT_PUBLIC_SUPABASE_KEY and NUXT_PUBLIC_SUPABASE_URL

[MichaelJCole]

Version

"@nuxtjs/supabase": "^1.5.0",
"nuxt": "^3.16.0",

Reproduction Link

https://github.com/MichaelJCole/nuxt-supabase-config-warnings

Steps to reproduce

clone repo
configure with .env

NUXT_PUBLIC_SUPABASE_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24iLCJleHAiOjE5ODM4MTI5OTZ9.CRXP1A7WOeoJeXxjNni43kdQwgnWNReilDMblYTn_I0
NUXT_PUBLIC_SUPABASE_URL=http://127.0.0.1:54321
NUXT_SUPABASE_JWT_SECRET=super-secret-jwt-token-with-at-least-32-characters-long
NUXT_SUPABASE_SERVICE_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6InNlcnZpY2Vfcm9sZSIsImV4cCI6MTk4MzgxMjk5Nn0.EGIM96RAZx35lJzdJsyH-qQwv8Hdp7fsn3W0YpN81IU

Notice the warnings.

What is Expected?

No warning and works as expected.

What is actually happening?

WARN Missing supabase url, set it either in nuxt.config.js or via env variable
WARN Missing supabase anon key, set it either in nuxt.config.js or via env variable

The supabase client seems to be configured, but tracking down the warnings was a bummer.