vue-meta VS i18n

Take a look at the repo for a workaround.

Working with metadata has its intricacies. That's why we suggest using Vue-meta while working with your app's metadata. This is a Vue.js plugin that allows nested components to overwrite each other's values and grants you the capability to replace and add metadata as needed. 💾 It also makes defining meta tags in the header simpler and is used by Nuxt.

There is really cool library called Vue Meta that is used for setting all the meta tags like title, description, and also open graph api.

Out of the box, Gridsome includes vue-meta, dynamic routing (no more v-router settings to setup for every page!), Single File Component development structure, and more! Whether you're an experienced Vueveloper or dipping your toes in, you'll have access to the power of the ecosystem where you need it while Gridsome handles a lot of the Vue setup management for you.

Has any of you ever used a module for meta keywords in vue/react/angular? Such as: https://vue-meta.nuxtjs.org/

Hey there, check out this section of the Inertia.js docs: https://inertiajs.com/pages#title-and-meta-tags. It explains how to set title and other meta data within an Inertia app. TLDR; Use https://github.com/nuxt/vue-meta.

vue-meta for vue 3 is here: https://github.com/nuxt/vue-meta/releases/tag/v3.0.0-alpha.0

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.