i18n VS auth-module

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.

Nuxt 3 comes with built-in utilities to support session and authentication. We are working on a new official module.

The evolution of nuxt-auth: there's nuxt/auth (Nuxt 2), an alternative module to try to bridge the gap for Nuxt 3 (and another one), and suddenly, sidebase/nuxt-auth popped up, which seems to wrap next-auth. I don't know if that's the proposed official solution going forward, reuse don't reinvent, or just a stop-gap measure (will the rug get pulled again?)

If you’re on nuxt 2 you can checkout the „old“ nuxt-auth which supports google and a lot of stuff surrounding it here: https://auth.nuxtjs.org/

If this is to do with user authentication and the API is using some kind of standard way of authenticating (e.g. a REST API) I would personally use https://auth.nuxtjs.org/ to do the heavy lifting for you.

Nuxt Auth module is very convenient to configure oauth and oidc authentication. And it wires everything in a project like routes, store, Axios interceptors etc..

Documentation

https://stackoverflow.com/questions/65642232/nuxtjs-how-to-use-httponly-cookies-for-nuxt-auth-strategy https://github.com/nuxt-community/auth-module/issues/142