devtools
devtools copied to clipboard
inspecting components randomly stops
Version
5.1.1
Browser and OS info
macOS Mojave 10.14.5 - Google Chrome Canary Version 77.0.3850.0 (Official Build) canary (64-bit) / Google Chrome Version 75.0.3770.100 (Official Build) (64-bit)
Steps to reproduce
It seems to be ramdom
What is expected?
On inspecting a component on the vue devtools, the component besides it should show the data and properties of that component
What is actually happening?
the component that show the data from the inspected element stays empty.
This bug happens to me way too many times and it's really stressing because sometimes refreshing or even cleaning the cache doesn't solve the problem
Same issue here. Sometimes I can browse the components for some time before it totally freezes. No component info will update after that, even after page reload, close+open Chrome itself. Sometimes it comes back after a very long idle time. vue-devtools 5.1.1 Windows 10 Google Chrome Version 75.0.3770.142 (Official Build) (64-bit)
reopen chrome devtool
@eightHundreds sometimes this works, sometimes it don't. Sometimes it works on the third or fifth time I tried. Anyway, It occurs too many times, what it seems to indicate that something is wrong.
Latest Chrome update (76.0.3809.100 ) seem to have fixed this issue completely 🕺
I'm still running the same problem in the Chrome 76.0.3809.100
I am still running into this issue on Chrome Windows 10 Chrome Version 77.0.3865.90 (Official Build) (64-bit) Vue.js devtools 5.1.1
I am using the below for development vuejs 2.6.10 npm 6.9.0 webpack-dev-server 3.8.1 with devServer for hot reloading
The vue component data shows correctly after the first load. A couple of changes to the files and webpack reloads the page and vue loses its component data The components are shown, but when you click the component, there is nothing on the right hand side Have to close the Chrome devtools and reopen for it to work again Sometimes, closing and opening also will not work - it is very random
I tried the same workflow on Firefox 69.0.2 (64-bit) - and there are no issues.
I'm having the same issue. If I enable debugging, when I click a component I see the next error:
Instance uid=app:54 not found
or
App with id _unmounted not found
I have realized it works by opening a new tab. Whenever webpack-dev-server triggers an update, it stops working.