vue-meta VS prerender-spa-plugin

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

With Vue3, its possible to pre-render each page with `https://github.com/chrisvfritz/prerender-spa-plugin` However, I would like to render each page to an actual html file, so that `vue-router` will not be used, but instead the server will take care of serving each page. Is that possible?

After investigation, the idea and the prerender-spa-plugin pre-rendering solution hit it off. The principle of the pre-rendering scheme can be seen in the following figure: