v1.0.21

New

• Component prop type can now be an array of types (@ealves-pt):

  props: {
    myProp: [String, Number] // can either be a string or a number
  }

• Most of the warnings now come with the name of the component it is found in (if a name is available).

• Runtime warnings now use console.error, which means they come with stack traces by default. Setting Vue.config.debug = true now only enables comment anchor nodes.

• orderBy filter improvements (@posva)

  The orderBy array filter can now accept:

  • multiple sort keys, or
  • an array of sort keys, or
  • a custom comparator function (same with the comparator used in Array.prototype.sort)

  See updated docs for examples.

• :class bindings now support using a string of multiple classes (@phanan):

  <div :class="{ 'a b c': true }"></div>

• track-by for v-for can now accept a path instead of a simple key.

Fixed

• #2567 fix IE9 inline style bindings that need vendor prefix
• #2573 ensure v-if and v-for compilation order is not dependent on appearance order. (v-for always comes first)
• #2580 initially invalid props should still be reactive
• #2593 fix explicitly setting Vue.config.devtools to non-default value
• #2606 prop coercion should be applied to default values (@simplesmiler)
• #2620 text parser should not remove newlines, also fix cache hit (@sirlancelot)