Skip to content

Releases: vuejs/vue

v1.0.10

23 Nov 20:00
Compare
Choose a tag to compare

Fixed Vue.version from 1.0.9.

v1.0.9

23 Nov 19:32
Compare
Choose a tag to compare

Known Issue

The distributed file on CDNs and NPM will expose the incorrect version (Vue.version = '1.0.8'). Fixed in 1.0.10.

New Build Setup

  • The source code now uses ES2015 modules and leverages a more efficient build setup. This results in slightly better script parse time and smaller build size.
  • When installed via NPM and used with a module bundler (Webpack/Browserify), the main file is now a pre-bundled single file (dist/vue.common.js), which should also make builds faster.
  • Contributors: please note the build setup has changed. Here's the updated instructions.

Fixed

  • #1797 v-model and vm.$set can now properly initialize non-existent dynamic paths such as "a[b + 'c']".
  • #1800 properly preserve whitespace inside raw HTML interpolations
  • #1806 avoid duplicate classes during transclusion
  • #1816 Fix error when using Vue.set and Vue.delete on objects created via Object.create(null) (@kazupon)
  • #1839 Fix event propagation check when there are chained emits.
    • Note this fix changes an undocumented behavior of vm.$emit: previously it returns the vm itself. Now it returns a boolean value representing whether the event should propagate. Do not rely on any behavior that is not officially documented.
  • #1850 Fix v-ref on elements with both v-for and v-if.
  • props with wrong types on initialization are now still set up with reactivity.

1.0.8

12 Nov 22:01
Compare
Choose a tag to compare

New

  • Added support for pre-defined getters/setters on data objects. This feature is off by default and must be turned on by setting Vue.config.convertAllProperties = true, since it comes with a small performance cost. (@jdavidberger)
  • v-on key modifiers now also support all single letters. (@yulon)
  • props options now supports using prop objects in array syntax again.

Fixed

  • Observer should no longer throw errors when trying to observe objects created via Object.create(null). (@kazupon)
  • Fixed an edge case in IE where text interpolations are not processed due to IE randomly splitting the text nodes into multiple adjacent ones.
  • #1778 fix incorrect warning for two-way binding on v-for alias
  • #1779 fix incorrect warning for v-ref on non-component elements
  • #1781 fix afterEnter hook firing before transition finishes
  • #1786 fix $event variable for v-on inline statement handlers with filters
  • #1791 avoid v-for re-rendering when using v-model on primitive values

1.0.7

06 Nov 17:27
Compare
Choose a tag to compare

Fixed

  • #1724 v-ref regression when used on <router-view>
  • #1727 Boolean props not working properly
  • #1729 Unnecessary is attribute warning

1.0.6

05 Nov 19:54
Compare
Choose a tag to compare

Skipped 1.0.5 because it contains an incorrect dist file.

New

  • The limitBy filter now also accepts a second argument which is the starting offset. (@Mat-Moo)
  • Added warning for mixed usage of mustache interpolation and v-bind for the class attribute.

Fixed

  • v-else should no longer insert the block multiple times when the condition changes from one falsy value to another falsy value.
  • #1669 Improved fragment instance ignored attribute check so it only warn at appropriate times.
  • #1671 $refs should be reactive for v-if checks
  • #1683 two-way props should sync properly when first mutating the value then replacing it.
  • #1695 $refs should be updated when switching between components with keep-alive
  • #1703 fixed an issue where IE treats an attribute and its v-bind: form as the same attribute. (@fergaldoyle)
  • #1717 v-show should properly skip transition when element is detached. Also fixed behavior difference in Firefox and Chrome.

1.0.5

05 Nov 19:46
Compare
Choose a tag to compare
[release] 1.0.5

1.0.4

31 Oct 20:41
Compare
Choose a tag to compare

New

  • Better warning for ignored attributes on fragment instances.

Changed

  • Custom directives now have a default priority of 1000. This should make it be bound before most of the built-in directives (except components, partials, slots and flow-controls, of course). This is part of the fix for custom directive dynamic params and should not break existing usage.

Fixed

  • Fixed dynamic params for custom directives not working properly. (@kazupon)
  • v-for context can now properly access parent scope's $els and $refs. (@TerenceZ)
  • v-bind on object and v-bind:class on object are now in deep mode as expected.
  • #1656 Fixed v-on filters not applied in correct scope when used with inline statements.

1.0.3

29 Oct 02:17
Compare
Choose a tag to compare

New

  • v-bind now support accepting an object without arguments, which would allow dynamic binding of multiple attributes:

    <div v-bind="{ id: someProp, 'other-attr': otherProp }"></div>

    Note when using this syntax to bind class and style, only plain string values would work.

  • limitBy filter:

    Limit the array to the first N items, as specified by the argument.

    <!-- only display first 10 items -->
    <div v-for="item in items | limitBy 10"></div>

Fixed

  • #1479 filterBy should no longer return duplicate objects when using multiple search keys.
  • User-defined component names should no longer be overwritten by option key names.
  • Fix edge case for v-for="(key, val) in obj" syntax where the key could be falsy. (@vprimachenko)
  • #1639 Fix title as prop edge case in IE10/11 (@fergaldoyle)

1.0.2

29 Oct 01:59
Compare
Choose a tag to compare

Not recommended. See 1.0.3 instead.

1.0.1

27 Oct 18:01
Compare
Choose a tag to compare

Fixed

  • v-for="(index, val) in array" now updates index properly.
  • Fixed a memory leak issue when when replacing arrays with overlapping objects.