supabase VS i18n

In this blog post, we will create a link shortener app (similar to bit.ly or dub.co) using NuxtJS and Supabase as the backend, leveraging Supabase's auth and database features. The Nuxt ecosystem already has an official Supabase module, making it easier to integrate Supabase with NuxtJS.

To work with Supabase in Nuxt, the best way is to use the official module that you can check out here.

Auth Issue: nuxt-modules/supabase#144

Supabase has an excellent DX that is well-documented. There's also the nuxt-supabase package and its documentation here - https://supabase.nuxtjs.org/.

I feel you. What helped me was referencing other nuxt 3 modules such as https://github.com/nuxt-modules/supabase

This is pretty much all you need: https://supabase.nuxtjs.org/

For my situation, I needed to use a Profile wrapper to handle this. Here is a link to a Github discussion for reference, in case anyone needs it: https://github.com/nuxt-modules/supabase/issues/50

For more, check out https://i18n.nuxtjs.org/

There is Nuxt 3 i18n - https://v8.i18n.nuxtjs.org/

GitHub repo

hostname (string) If you define the hostname, it will be overridden for all the routes, regardless of the application domain. Module logic is that if the hostname is not defined, the application checks if the current request is HTTPS or not, and gets the current application domain. Then, the module builds a hostname based on that. If you use nuxt-i18n and your app has several domains, the module should clearly define the current application based on the requesting domain.