Open cco3 opened 7 months ago
@nuxtjs/supabase: 1.1.7 nuxt: 3.11.1
Use NUXT_PUBLIC_SUPABASE_URL and NUXT_PUBLIC_SUPABASE_KEY in your .env file as suggested here: https://supabase.nuxtjs.org/get-started#installation
NUXT_PUBLIC_SUPABASE_URL
NUXT_PUBLIC_SUPABASE_KEY
.env
Include these in your runtime config:
runtimeConfig: { public: { supabase: { key: "", url: "http://127.0.0.1:54321", }, }, },
No warnings are given.
A warning is given because the key is set to an empty string (even though it is overridden with NUXT_PUBLIC_SUPABASE_KEY.
https://github.com/nuxt-modules/supabase/blob/f3f11aa4642985551c9fd3237f93124482e6a17b/src/module.ts#L148
I would expect the module to allow me to override the value before deciding to give me a warning, but it reads the config directly.
Version
@nuxtjs/supabase: 1.1.7 nuxt: 3.11.1
Steps to reproduce
Use
NUXT_PUBLIC_SUPABASE_URL
andNUXT_PUBLIC_SUPABASE_KEY
in your.env
file as suggested here: https://supabase.nuxtjs.org/get-started#installationInclude these in your runtime config:
What is Expected?
No warnings are given.
What is actually happening?
A warning is given because the key is set to an empty string (even though it is overridden with NUXT_PUBLIC_SUPABASE_KEY.
https://github.com/nuxt-modules/supabase/blob/f3f11aa4642985551c9fd3237f93124482e6a17b/src/module.ts#L148
I would expect the module to allow me to override the value before deciding to give me a warning, but it reads the config directly.