v0.5.1

fixes a broken test

v0.5.0

• vue-meta now sanitizes/escapes rendered outputs
• addition of __dangerouslyDisableSanitizers option to disable sanitization

v0.4.4

• Fixed a regression in #22 that broke server-side rendering (#23 - credit to @atinux)
• Added a check for undefined computed $option to prevent runtime reference errors

v0.4.3

Added a fallback to setTimeout where requestAnimationFrame is unavailable in batchUpdate

v0.4.1

Fixes a bug where undefined vmin caused invalid markup - props to @atinux for the fix!

v0.4.0

vue-meta now watches data for changes, so calling $meta().refresh() after an asynchronous action is no longer necessary. vue-meta will just do this automatically. As with mount data, the update that is performed to the DOM is batched to prevent extraneous re-rendering.

v0.3.0

This version adds support for custom options:

Vue.use(Meta, {
  keyName: 'metaInfo', // the component option name that vue-meta looks for meta info on.
  attribute: 'data-vue-meta', // the attribute name vue-meta adds to the tags it observes
  ssrAttribute: 'data-vue-meta-server-rendered', // the attribute name that lets vue-meta know that meta info has already been server-rendered
  tagIDKeyName: 'vmid' // the property name that vue-meta uses to determine whether to overwrite or append a tag
})

v0.2.0

• Breaking Change: You now have to define metaInfo as a function in order to access component props/data. This is in contrast to previous versions where each property of metaInfo had to be a function. This fixes a bug (#14) to do with items in a tag list being overriden.

v0.1.1

• include correct files on npm

Initial Release

• Bare-minimum testing setup
• Bare-minimum features