I've been using the above for the last month and it's a far superior way of building components IMO. I've been able to reduce the amount of unneeded observer watchers and tracked properties by about 50%.
The distinction between simple raw JS objects and functions and what are Vue-tracked/computed properties makes the whole thing feel cleaner.
Typescript integration is also much better and doesn't feel like a hack like the Class component approach did.
Plus the eventual tree-shaking benefits of importing only the parts you need is great.
Agreed. I'm in the middle of moving our code base over to the plugin above. I figured the Typescript + Decorators Component API was a dead end, so it'd be easier to transition from the plugin to Vue 3 when it eventually came out.
It's been a breath of fresh air when working with typescript.
It integrates just fine with old Vue 2 components. So the transition is very simple, much like Typescript.
I don’t think most people critiquing the new composition API have really tried it. This is not something you can get a good sense for just by looking at RFC API style docs.
It encourages better modern JS and simpler code which really matters in large projects. This brings Vue closer to simple JS functions instead of giant magic-y options interfaces, while still being fundamentally the same with templates/computed props/lifecycle/etc.
https://github.com/vuejs/composition-api
I've been using the above for the last month and it's a far superior way of building components IMO. I've been able to reduce the amount of unneeded observer watchers and tracked properties by about 50%.
The distinction between simple raw JS objects and functions and what are Vue-tracked/computed properties makes the whole thing feel cleaner.
Typescript integration is also much better and doesn't feel like a hack like the Class component approach did.
Plus the eventual tree-shaking benefits of importing only the parts you need is great.