Skip to content
Jun 6, 2021
chore(release): 3.0.0-alpha.9

@pimlie pimlie released this Jun 6, 2021


  • add plugin for options api support (0745f16)
Assets 2

@pimlie pimlie released this Apr 4, 2021


  • add fully static / client-only example (c6c3b47)
  • make createMetaManager util args optional (use defaults) (89d7f58)

Bug Fixes

  • dont call clean before starting dev server (683ea9c)
  • fix/improve resolver types (fcb47a9)
  • only match vue-meta in jiti alias (2b8c5e8)
  • replace node-env in rollup config (ed6ba9f)
  • use dynamic import for vue server-renderer (8e2fed1)
Assets 2

@pimlie pimlie released this Feb 28, 2021


  • add support for computed metadata
  • add onRemoved guard
  • wait for component element to be removed from the DOM before removing metadata to prevent flash during page transitions

uses a MutationObserver, might need a polyfill but afaik any browser supporting Proxy also supports MutationObserver

  • some code cleanup
  • show active metadata in vue-router example
  • improved styling a bit of vue-router example
Assets 2

@pimlie pimlie released this Jan 31, 2021


  • Renamed useMetainfo to useActiveMeta
  • Export types
Assets 2

@pimlie pimlie released this Jan 25, 2021

The first alpha release for vue-meta v3 supporting Vue 3, basic functionality should work but needs lots more testing. Don't use this in production. Help with squashing bugs would be appreciated.

Quick overview of features


See ./examples/vue-router for a working example

import { watch } from 'vue'
import { useMeta, useMetainfo } from 'vue-meta'

export default {
  setup () {
    // add meta info. The object passed into useMeta is configurable
    const { meta } = useMeta({
      title: 'My Title'

    // get the currently used metainfo
    const metadata = useMetainfo()

    watch(metadata, (newValue) => {
      // metadata was updated, do something


See ./examples/ssr for a working example

import { createSSRApp } from 'vue'
import { renderToStringWithMeta } from 'vue-meta'
import { App, metaManager } from './App'

export function renderPage() {
  const app = createSSRApp(App)

  const [appHtml, ctx] = await renderToStringWithMeta(app)

  return `
  <html ${ctx.teleports.htmlAttrs || ''}>
    <head ${ctx.teleports.headAttrs || ''}>
     ${ctx.teleports.head || ''}
    <body ${ctx.teleports.bodyAttrs || ''}>
      <div id="app">${appHtml}</div>
     ${ctx.teleports.body || ''}

Meta Resolvers

needs more attention + real world testing

In vue-meta v2 there was limited control on which metadata to show if you had multiple components returning the same information.

In v3 we introduce meta resolvers, these are functions that should give you full control on which data to show when multiple options exist.

See eg ./src/resolvers/deepest and ./examples/vue-router/main. The deepest resolver uses the data of the component with the highest depth (from the $root component). The resolver in the vue-router example just returns the data of the newest component (highest _uid).

Metainfo Component

Adding this component is currently required, but it will eventually be optional

Add a Metainfo component in your app to extend the used metadata using slots.

  <div class="my-layout">
      <!-- // content contains the value active value for base from `useMetainfo` -->
      <template v-slot:base="{ content, metainfo }">{{ content }}</template>
      <template v-slot:title="{ content, metainfo }">
        {{ content }} - {{ metainfo.description }} - Add the description to the title

Known Issues

  • Metainfo component has to be present otherwise client side updates wont work
  • The error Uncaught ReferenceError: body is not defined is logged in the browser
    Solution: Add a body slot to your metainfo component with an empty tag: <metainfo><template v-slot:body><span/></template></metainfo>
  • Types are wrong (still pointing to v2 types)
Assets 2