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
There seems to be a bug where all the computed properties from all previously inspected components accumulate in the devtools, displaying as undefined, or old values. So you might end up selecting a component with no computed properties, and seeing this:
Seen on v7.6.1 of the extension, Vue v3.4.11, Chrome 130.0.6723.92, Windows 10
Edit: this seems worse than I first thought, it seems the hooks into Vue are actually causing these computed properties to get attached to components that shouldn't have them? I've started getting this warning which goes away when the extension is disabled:
[Vue warn]: Computed property "id" is already defined in Props.
The text was updated successfully, but these errors were encountered:
There seems to be a bug where all the computed properties from all previously inspected components accumulate in the devtools, displaying as
undefined
, or old values. So you might end up selecting a component with no computed properties, and seeing this:Seen on v7.6.1 of the extension, Vue v3.4.11, Chrome 130.0.6723.92, Windows 10
Edit: this seems worse than I first thought, it seems the hooks into Vue are actually causing these computed properties to get attached to components that shouldn't have them? I've started getting this warning which goes away when the extension is disabled:
The text was updated successfully, but these errors were encountered: