search

vuejs / devtools-v6

⚙️ Browser devtools extension for debugging Vue.js applications.
https://devtools-v6.vuejs.org/
MIT License
24.68k stars 4.15k forks source link

Component list not updating in Inspector after update #1707

Open tr00ks opened 2 years ago

tr00ks commented 2 years ago

Version

6.0.2

Browser and OS info

Chrome, macOS Monterey

Steps to reproduce

I was working with the previous version of vue devtools in chrome, then it crashed and I had to reload the extension from the chrome extensions page. I then went back to my app, closed chrome devtools, reloaded the page, opened chrome devtools again, and went to vue devtools. I am now seeing the new version of vue devtools. After clicking through the modal that says what's new, I land on the Inspect tab with the components list. Now is when the components list doesn't change when I navigate pages, open modals, or anything. Using the little "Select component in the page" doesn't work, either. Nothing I click with that updates the components list in vue devtools. I've tried closing and reopening chrome devtools and reloading my app. Now the component list is empty. The app selector only has "No app" as an option, not sure if that is a factor.

What is expected?

The components list to be reactive and update according to app behavior

What is actually happening?

The dev tools component list is "frozen"

Version I put above is 6.0.2 is of the vue devtools extension, according to chrome's manage extension page

Akryum commented 2 years ago

That's a very strange behavior. You don't have any error? Could you put together a runnable reproduction? Because I don't reproduce this on any app I have . Thanks

bah87 commented 2 years ago

I'm seeing the same issue on Chrome and FireFox with macOS Big Sur. We are converting from AngularJS to Vue using ng vue, so maybe that is part of it

About7Sharks commented 2 years ago

Same issue on Brave, and Chrome (using Vue2 on linux).

solocommand commented 2 years ago

I was going to report the same issue on Chrome 98, but it looks like the underlying issue (at least for me) is that the components (which are registered to a single Vue instance) are now broken out into individual apps.

image

Admittedly I skipped through the What's New info, so if that change was covered there it's just user error on my part.

Akryum commented 2 years ago

Admittedly I skipped through the What's New info, so if that change was covered there it's just user error on my part.

Yup. 🐈

image

About7Sharks commented 2 years ago

This issue is now fixed with the latest version of vue dev tools. I'd suggest closing this Issue.