Vue.js 0.10.6, and what's next

Jul 29, 2014

0.10.6

Vue.js 0.10.6 has been released! This is another small bug-fix release and will be the last maintainance version before the next major release.

• fix v-style error when value is falsy or a number. ( thanks to @dmfilipenko )
• fix the built-in currency filter error when value is a string ( thanks to @dmfilipenko )
• fix Vue.require for building with Component v1.0+ ( thanks to @kewah )
• Allow template nodes to be passed as a template option ( thanks to @jordangarcia )
• vm.$destroy() now accepts an optional argument noRemove. When passed in as true it will leave the vm’s DOM node intact after the vm is destroyed.

Vue-next

Some of you might have noticed there is a next branch in the repo. And yes, I am re-writing Vue.js from scratch. There are two main reasons:

• Fix some issues that are caused by design flaws in the current version. Because these changes affect the design of some core modules, it is actually easier to rewrite than to apply on the current codebase.
• Improve general code quality (in particular, compiler.js as of now is a big pile of mess, and comments are not consistent across the codebase.)

Take note that the next branch is still in very early stage. The internals will change a lot, and when it comes out it will break current applications. Despite that I will try to keep the API changes to a minimum. Major differences with current 0.10 branch are documented in changes.md. The list is obviously incomplete and subject to change, some of them are simply ideas, but it at least gives you a taste of what to expect, and I’d appreicate your feedback on any of the topics.

Share your thoughts at vuejs/Discussion.