-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vuex 4 devtools integration #1942
Comments
Thank you @Akryum for sharing this update! It gives a lot of peace of mind. Edit: Better wording. |
It is very annoying that vue3 is out for a long period now and still other components not working well like Vuex. Is it so very hard to implement this? I think that there are a lot of developers who love to see it working asap. Please take priority of this issue. |
@marcelruiter Yes, your majesty. At once, your majesty! |
In the meantime, while this has not been merged and rolled out, is there a workaround we can use to debug the Vuex store? |
@dhruvkb you could fork the repo, merge the pull request and use your forked vuex version. |
close #1942 Co-authored-by: Eduardo San Martin Morote <[email protected]> Co-authored-by: Kia King Ishii <[email protected]>
Released in 4.0.1 |
Thank you @Akryum for your dedication on this ! |
The API for Vue Devtools 6.x is now documented here.
I open this issue so we can keep track of the Vuex 4 integration.
The text was updated successfully, but these errors were encountered: