You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"Custom Renderer API: a first-class API for creating custom renderers will be available, and no longer requires forking the Vue codebase with custom modifications. This will make it much easier for render-to-native projects like Weex and NativeScript Vue to stay up-to-date with upstream changes. It would also make it trivially easy to create custom renderers for various other purposes."
Can we hope for a first-class-citizen Vue in Meteor in 2019? :)
The text was updated successfully, but these errors were encountered:
Actually that's maybe not the relevant part. Features split into multiple packages will actually help, because we will be able to swap Vue reactivity system with another Tracker-compatible one.
Just read this article: "Plans for the Next Iteration of Vue.js" https://medium.com/the-vue-point/plans-for-the-next-iteration-of-vue-js-777ffea6fabf#---0-387
This part recalled me this fork:
"Custom Renderer API: a first-class API for creating custom renderers will be available, and no longer requires forking the Vue codebase with custom modifications. This will make it much easier for render-to-native projects like Weex and NativeScript Vue to stay up-to-date with upstream changes. It would also make it trivially easy to create custom renderers for various other purposes."
Can we hope for a first-class-citizen Vue in Meteor in 2019? :)
The text was updated successfully, but these errors were encountered: