Open skmbr opened 3 years ago
Hi @skmbr,
Sorry for the delay in getting back to you.
It does not, yet. I should find time to do this officially but I'm stretched on other projects right now.
I'm hoping to hit some milestones in the next couple of weeks though, and then I think I should take some time to look at this.
There was a decision made a while back to make Vue Class Component a dependency of Vuex Pathify a while ago; I will probably need to look at that again (it wasn't really my area, and ended up being a community PR).
Is this a blocker for you in the meantime? Did you manage to make it work in Vue 3?
Click the label to see all Vue 3-related posts.
Hi @davestewart ,
No worries, thanks for getting back to me!
Apart from the warnings it all seems to be working fine! Since they are just warnings it shouldn't be a major blocker, and I'm probably at least a month away from releasing this version of my app, but I thought it would be worth raising - even if (or especially if) it led to me finding out I was just doing something stupid! :)
Thanks again, and thanks for all your work!
No worries! And thanks for letting me know anyway :)
Feel free to bug me if I don't make any updates 😬
Will do! But not too soon! :)
Describe the bug As soon as I import vuex-pathify anywhere I see this warning in the console, always four times in a row:
Expected behaviour No warnings in the console
Additional context I've found similar posts from users of vue-bootstrap that suggest that package doesn't support vue 3 yet. Is this the case here?
Here's an example of a user having a similar problem with vue-bootstrap: https://stackoverflow.com/questions/63768491/export-default-imported-as-vue-was-not-found-in-vue