New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
devtool does not appear #2138
Comments
This is happening for myself and my coworker all of a sudden. It was working before my last meeting and now its not working. I think the latest update broke something |
me also - since 14 Feb v6.6.0. |
This isn't a solution but the Standalone version does work: I'm running Chrome 121.0.6167.184 on Mac OS with Vue.js devtools 6.6.0 installed from the Chrome Web Store and I'm not seeing the Vue Dev Tools tab either. |
Also here. Looks like something was broken after the last update (14/2) |
I've disabled the latest version and reinstalled the legacy version which seems to be working for now - Legacy v5 |
Thanks, worked for me. |
Since last version I see the Vue tab but every time the page gets refreshed the plugin stops working and I have to close and reopen the tab. This didn't happen with legacy version. |
@Akryum I don't know how else to help you to reproduce the error. When I click on the vue logo it does not open the dialog box in the new version. Grabacion.de.pantalla.desde.15-02-24.09.04.38.webm |
Can you try:
and report back? |
I'm having the same issue on mac and chrome |
When you are trying to reproduce the issue are you on the right version of
devtools? You might have to go to the extensions manager and force an
update on Vue devtools.
Also, does the legacy extension work with Vue 3?
…On Thu, Feb 15, 2024, 6:58 AM Pablo Raissiguier ***@***.***> wrote:
I'm having the same issue on mac and chrome
—
Reply to this email directly, view it on GitHub
<#2138 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIXZP4ZOTIWP7UUHZWHE7K3YTYA7NAVCNFSM6AAAAABDI5YQ3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBWGA2DSNRSGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I found out that using the incognito mode of chrome if the devtool appears, I tried other browsers and it works fine. I tried rebooting, reinstalling and it still doesn't work in normal mode. What could be the problem? attached pictures It detects that vue exists but when selecting the devtool icon it does not open the tool, nor does it appear in the header. Also try disabling all browser extensions. |
Could you try clearing the extension storage? Make sure to have 'Developer mode' enabled in the Extensions page: Open the extension menu and click on 'Inspect Popup': In the Chrome devtools that opens, go to the 'Application' tab and right-click on the item below 'Local storage' and click on 'Clear': |
This didn't work for me. I also installed the 6.6.1 and it still didn't resolve it. In fact, now I can't inspect the popup anymore |
Does it work in edge? |
Same here, doesn't work on brave.
Same, can't inspect the popup EDIT: downgrading to 6.5.1 works 👍 |
Same issue on Chrome 121.0.6167.185 Windows 11. The panel just stopped opening within the last 2 days. Restarted the everything, tried the cache clearing from a few posts above. It's not site specific. Edit: the downgrade to 6.5.1 fixed it for me too. 6.6.0 looks like a big update, must be something causing problems in there. |
I tried everything because the 'pinia' option didn't appear, but this is the only thing that has worked for me |
@skjnldsv Thank you for this, |
The extension randomly stopped working for me using Brave. Was using it for years with no issues. I also tried re-installing the legacy version and that also wouldn't work. I cleared every setting I could in Brave and neither would work. I did notice it worked in incognito, however. I restarted my computer. No effect. Not sure if a Brave or extension issue. Edit: I've never users the Brave profile functionality but perhaps that would help mitigate any loss of preferences, settings, etc. |
Maybe it's somehow caused by the migration to Manifest V3... |
Hey guys, it seems that FORCE REFRESH can be helpful. My setps are:
Hope this trick can inspire somebody to resole this. @Akryum are there something wrong with extension initilization lifecycle? Version 1.62.165 Chromium: 121.0.6167.184 on Windows 11. Vue 2.7 load from cdn. |
vue-dev tools not working any more |
I have the same problem, it does not work in normal chrome profiles. Maybe it's helpful for debugging the problem. |
i followed @mohamad68 which did not work but after following @urbgimtam it started working, thanks everyone |
Looks like something is wrong with the service worker (Manifest V3) :( |
I also got it working after following the steps by @mohamad68 and @urbgimtam. The Chrome update put me on version 122.0.6261.58. |
Worked too! Thanks @mohamad68 ! |
A note for those using Vue 3 and Vite, you can use this plugin or app instead: |
This 100% fixed it for me. |
The solution of @urbgimtam works for me on MacOS Chrome 🙌🏻 |
Worked remove 'update on reload'. |
@mohamad68 removing "update on reload" check worked for me, thanks! |
I cleared all the storage but the "Update on reload" checkbox was not checked for me so that hasn't solved it in my case. |
Hello, is there any update? Does the newest version work? |
For me the "Update on reload" fix is only temporary, and I have to toggle it on and back off to get devtools to reload again after a while. |
This issue is affecting many users and can be easily reproduced. The label should be updated. Unchecking the Service Workers' "Update on reload" is the only temporary fix that worked for me. |
Mine can be displayed, but once I use the middle of the mouse to close the vue devtools TAB, I won't be able to find any entry to re-add it, only to reopen the console |
Unfortunately, I can't see it anymore, even after unchecking the Service Workers' "Update on Reload", when using Nuxt > 3.10.x. and VueDevtools 6.6.1. It works with Vue directly (maybe some of the latest updates of both Nuxt and Vue Devtools created the issue?). Its a really strange behaviour. The extension detects the presence of Nuxt+Vue, and its even present on the DOM. But never shows up on the Chrome devtools. Same behavior on Firefox, which may help to understand if its a direct bug or a Chrome caching issue. As a last resort, I've tried to use Vue Devtools standalone, but it also errors out saying:
Anyone found out more? |
Unchecking the Service Workers' "Update on reload" worked for me too. |
The same problem with VueDevTools 6.6.1 Windows 11 Tested on Nuxt 3.11, Vue 3.4.21 apps... |
Ok, another weird behaviour that could help tracking this. On an existing project with Nuxt 3.10.3 and Vue 3.4.20 (don't remember the Nitro version), Vue devtools was detected and its tab appeared on Chrome Devtools. Funny thing is created new Nuxt project with Nuxt 3.10.3, Vue 3.4.20 and even downgraded Nitro to 2.9.0, removed node modules/ and package-lock.json, and still I can't get Vue Devtools to show up again. Could it be one of the dependencies? |
Downgrading nuxt devtools to 1.8.0 seems to allow VueDevtools to work again. nuxt/devtools#634 |
Also vue-devtools can be downgraded to 5.6, but for me it isn't comfortable |
Thanks. Disabling Nuxt Devtools made Vue Devtools panel appear again. |
I have same problem on macOS using Chrome. |
Fixed in @nuxt/devtools 1.1.5. |
The same issue: Don’t have any other devtools. |
This worked for me as well, thank you! |
Vue devtools version
6.6.0
Link to minimal reproduction
https://github.com/PabloBagliere/vue2-error-devtool-quasar
Steps to reproduce & screenshots
to execute the problem is:
What is expected?
It is expected to show the vue devtool option.
Example:
What is actually happening?
Does not display the vue devtool
System Info
Any additional comments?
I use google chrome
I use quasar version 1 since the project at work is old. Vue already comes in quasar and uses vue 2.7.15.
The packages I have installed are in the image
I tried to use legacy but it does not work well because the project uses the setup method in many components and legacy does not show the setup.
The text was updated successfully, but these errors were encountered: