Closed bsiguret closed 3 weeks ago
Same issue here. Here's my empty state, showing some console logs, as well as the location in the code of the log issue, not sure how helpful it is but π€·
Try to fix it in v7.6.1 (pending review), Please help me confirm whether it is fixed when it passes the audit on chrome store, thank you
@webfansplz Not fixed for me in v7.6.1, the same problem.
I don't see your PR changes in the source code (the optional chaining) and I don't think this is normal. I tried to remove and reinstall the extension + restart my browser without change. Should I do something else?
Thank you π
@webfansplz Not fixed for me in v7.6.1, the same problem.
I don't see your PR changes in the source code (the optional chaining) and I don't think this is normal. I tried to remove and reinstall the extension + restart my browser without change. Should I do something else?
Thank you π devtools-chrome.zip Can you try this zip?
@webfansplz Not fixed for me in v7.6.1, the same problem. I don't see your PR changes in the source code (the optional chaining) and I don't think this is normal. I tried to remove and reinstall the extension + restart my browser without change. Should I do something else? Thank you π
devtools-chrome.zip @bsiguret Can you try this zip?
@bsiguret I have just released v7.6.2 and await review. You can also try again after passing the review (if there is any latest news, please let me know, thank you).
@bsiguret Can you try this zip?
@webfansplz No change with the zip sorry π’ I'll test the 7.6.2 if you changed something. Have a nice evening π
@bsiguret Can you try this zip?
@webfansplz No change with the zip sorry π’ I'll test the 7.6.2 if you changed something. Have a nice evening π
This is a bit strange, can you again make sure to uninstall all Vue devtools in case and restart the browser to try to install it? (I reproduce the issue yesterday and confirmed that I had fixed it
@wynged How about you? Itβs working fine for you?
@webfansplz maybe it will be fixed later. When I check the source file of the error, I see that it comes from a node_module vue -> devtools-core. I don't know how the package works with the extension so maybe I'll need to wait for a Vue and then a Nuxt version update.
I'm sorry if I'm making a dumb error. Anyway, it's not blocking my development since I can work with the previous version just fine. I'll wait a couple of weeks and ping you again on this issue if necessary.
Thank you for your time π
it's working better..... I saw some state, but when I popped up a modal in my app and tried to select the modal to view it's state the state wouldn't update, although I was scrolled to the component in the tree on the left. When I closed the modal I got the state to swap when I selected other components, but I also saw this error.
It did seem to get better when I tried again, but when I first popup our modal it doesn't seem to be something that the component picker can see, it doesn't get highlighted at all.
Hello! Everything is in the title:
My Vue Devtool extension updated itself to v7, and I have trouble with most of my components having no state showing in the browser extension.
I went back to the v6 version to fix it.
The project is on Nuxt v3.13.2 (associated with vue v3.5.5)
Here are screenshots of what I'm saying:
v6
v7
I investigated a bit and the components that aren't working are inside a v-for, but it's not a 100% fail rate and maybe not true.
I can't share the project since it's a private project