Releases: ngsru/vue-server
Releases · ngsru/vue-server
0.4.5
Fixed
<slot>
API: spaces and line brakes interpretation improved<slot>
API: now works withv-for
-ed slots and slots nested deep inside template- properties defined via
Vue.prototype
now could be used inside v-for instances v-for
vm-instances now inherit parent's methods which names begins with$
or_
- in strict mode components now able to invoke themselves
Changed
$refs
/$
and$els
/$$
containers linking method changed (because of performance issue)- pseudo-reactivity improved: props pulled by component won't be overridden if parent's value didn't change
New
activateBe
now triggers global rebuilding to include$root
data changes insideactivateBe
0.4.4
Fixed
<slot>
got extensive fix. It appears before it was literally broken (could only handle the most simple cases). Now it's almost OK. But still there are some inconsistency compared to Vue.js behavior in cases with empty rendered provided content- fixed
compiledBe
hook and its mixins firing conditions and order - fixed an issue when a property with defined type causes an error when provided
undefined
value - fixed an error while building empty-templated components
class
andstyle
attributes merging order was fixed to produce the exactly same result as Vue.js does.- fixed issue when global asset registration functions didn't return the compiled asset.
New
- added most simple example for working with async data
0.4.3
Fixed
- components whose templates has multiple top level elements are now work correctly
- an issue when synchronous call of
done
callback insideactivateBe
won't work v-for
now work with plain numbers fetched from a variable
Changed
- errors that occur while executing expressions are now printed in 1 line (vs 4 lines before)
0.4.2
0.4.1
0.4.0
We have now tested version 0.4.0
on our big project and it seems to work fine. So, letting go of beta
prefix now.
Though, some bugs could appear, of course.
Fixed
- $logger removed from vm scope to prevent overlapping with possible public method
New
- Now possible to use
v-on:
directive on components to user cross-VM comunication. Could be removed in future because it can get in the way of client-only features - Thanks to the issue added new example (
examples/server-express
) onexpress.js
vue-server
got slightly faster :)
0.4.0-beta.8
Fixed
- UpperCamelCase component names are now properly converted into tag names. Example:
MyComponent
->my-component
New
- Now able to extend instances via
Vue.prototype.$myMethod = ...
principle
0.4.0-beta.7
Fixed
- an issue with error in global assets registration
- global partial template precompilation now works
- removed unused dependency
colors
0.4.0-beta.6
New
Vue.mixin
support (http://vuejs.org/api/#Vue-mixin)
Fixed
- an issue with wrong Boolean type props validation
v-repeat
&v-for
now accepts compound paths likeitems[name]
0.4.0-beta.5
Fixed
- fixed an issue with
props
when propertydefault
value converted toundefined
if it'sfalse
/null
/0
/''
- fixed
v-show
andv-if
behavior withv-repeat
to match original Vue.js functioning