You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
No errors. Seems that for each component state, render & currentRoute are accessed while not being defined on that particular component, causing the vue warn handler to kick in.
What is actually happening?
A load of warnings are printed, filling the complete console output.
It seems to happen when the page you're working is being reloaded: the extension does not pick up this reload at all (old components and values are still being shown, and it is no longer possible to navigate at all). When reopening the Edge devtools (which seems to restarts the vueks/devtools) the errors start for me.
I strongly suspect this is related to the reload behaviour, which is reproducible on https://sfc.vuejs.org/. Steps:
Open the playground
Open the devtools
See the value of the msg ref change when typing in the default input field
Refresh the page
vuejs/devtools is no longer connected to the page being shown, navigation doesn't do anything, values are not updated etc.
Reopening the complete devtools and with it the vuejs/devtools solve the issue
Vue devtools version
6.6.0
Link to minimal reproduction
None
Steps to reproduce & screenshots
What is expected?
No errors. Seems that for each component
state
,render
¤tRoute
are accessed while not being defined on that particular component, causing the vue warn handler to kick in.What is actually happening?
A load of warnings are printed, filling the complete console output.
System Info
Any additional comments?
This started this morning, so with the 6.6.0 update.
I do not have a usable repro yet.
The text was updated successfully, but these errors were encountered: