i've been researching to see if this would be worth migrating to and i have been wondering the same. @championswimmer did reply in a thread not that long ago, saying that's he's waiting for vue 3 release, so its not completely dead. i would imagine he's got a few things going on and has to prioritize his time, just like the rest of us. it would be nice to have some assurance before adding a new dependency, especially with vue 3 around the corner.
The main reason I'm not much active is because I am waiting on Vue 3 stability. The Vuex API needs to freeze.
I want to do a ground up rewrite of this post that.
This version will remain supported, and while I intend to make no breaking change to the API. It will be semver major update and will incorporate Vuex new pattern of createStore instead of earlier style.
I use Vue on multiple daily projects, so yes, if not for you guys, I just need to keep this maintained for my own projects :)
@championswimmer cool, then please, that means you have to extend somehow your modules yes? How you do that, because ClassA extends ClassB does not work. Tell us please, do you use mixins or what to share common methods and properties between modules?
offtop: thanks for library @championswimmer
Most helpful comment
The main reason I'm not much active is because I am waiting on Vue 3 stability. The Vuex API needs to freeze.
I want to do a ground up rewrite of this post that.
This version will remain supported, and while I intend to make no breaking change to the API. It will be semver major update and will incorporate Vuex new pattern of createStore instead of earlier style.