devtool does not appear

[PabloBagliere]

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:

• install dependeny (pnpm i)
• run (pnpm dev)

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

System:
    OS: Linux 6.5 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
    CPU: (6) x64 Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz
    Memory: 19.58 GB / 31.21 GB
    Container: Yes
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.10.0 - ~/.nvm/versions/node/v18.10.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.10.0/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.10.0/bin/npm
    pnpm: 8.7.3 - ~/.local/share/pnpm/pnpm
  Browsers:
    Brave Browser: 121.1.62.162
    Chrome: 121.0.6167.184

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.

[SkySor44]

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

[WeepingBoil]

me also - since 14 Feb v6.6.0.
Broken?

[Akryum]

I can't reproduce with the provided repo on Chrome/Linux.

[brentmitch]

This isn't a solution but the Standalone version does work:
https://devtools.vuejs.org/guide/installation.html#standalone

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.

[GuyGeva93]

Also here. Looks like something was broken after the last update (14/2)

[ajlond123]

I've disabled the latest version and reinstalled the legacy version which seems to be working for now - Legacy v5

[GuyGeva93]

I've disabled the latest version and reinstalled the the legacy version which seems to be working for now - Legacy v5

Thanks, worked for me.
Still it is truly necessary to fix the latest version.

[AndrianLeah]

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.

[PabloBagliere]

@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.
In the video you can see that the dialog box does not open and the devtool does not appear and I use the example repository that I gave you.

Grabacion.de.pantalla.desde.15-02-24.09.04.38.webm

[Akryum]

Can you try:

• restarting chrome
• restarting the computer
• another browser such as Firefox or Edge

and report back?

[pabloraissiguier]

I'm having the same issue on mac and chrome

[SkySor44]

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: ***@***.***>

[PabloBagliere]

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

Incognito mode

Standard mode

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.

[Akryum]

Check that the extension has 'Site access' setting set to 'On all sites':

[Akryum]

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':

[SkySor44]

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

[PabloBagliere]

It didn't work, directly the localstorage is empty, maybe the error is there because the localstorage is never filled with any value.
image of how I have the localstorage

[Akryum]

Does it work in edge?

[PabloBagliere]

Yes in edge and breave (firefox did not update the version) that seems to me the strangest thing so I started the issues.

Example photo

edge:

Brave:

[skjnldsv]

Same here, doesn't work on brave.
Version 1.62.165 Chromium: 121.0.6167.184

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

Same, can't inspect the popup

EDIT: downgrading to 6.5.1 works 👍
nhdogjmejiglipccpnnnanhbledajbpd-6.5.1.zip (rename to crx)

[jsodeman]

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.

[Joshwawo]

Same here, doesn't work on brave. Version 1.62.165 Chromium: 121.0.6167.184

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

Same, can't inspect the popup

EDIT: downgrading to 6.5.1 works 👍 nhdogjmejiglipccpnnnanhbledajbpd-6.5.1.zip (rename to crx)

I tried everything because the 'pinia' option didn't appear, but this is the only thing that has worked for me

[udithishara]

@skjnldsv Thank you for this, v6.6.0 broke most of the stuff and slow compared to v6.5.1, only solution was to rollback to a previous version for me

[Zenkylo]

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.
I uninstalled and re-installed Brave. No effect.
I uninstalled and purged everything Brave on my computer. On Mac this was /Users/{user}/Library/Application Support/BraveSoftware, then reinstalled Brave and installed the extension. This worked. However, I've lost all my browser preferences, settings etc., which I was prepared for. Quite a damper on my workflow. I'd suggest at least exporting your bookmarks before you do a fresh re-install.

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.

[Akryum]

Maybe it's somehow caused by the migration to Manifest V3...

[AdoKevin]

Hey guys, it seems that FORCE REFRESH can be helpful. My setps are:

1. closing the chrome developer tools,
2. FORCE REFRESH (Ctrl + F5 or Ctrl + Shift + F5 depends on your setting) the page,
3. open chrome devtools again. Finally, I got the Vue DevTools again.

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.

[mohamad68]

vue-dev tools not working any more

[vogtm]

I have the same problem, it does not work in normal chrome profiles.
For me, it actually works and appears in Incognito tabs.

Maybe it's helpful for debugging the problem.

[bksubramanyarao]

i followed @mohamad68 which did not work but after following @urbgimtam it started working, thanks everyone

[Akryum]

Looks like something is wrong with the service worker (Manifest V3) :(

[jsodeman]

I also got it working after following the steps by @mohamad68 and @urbgimtam. The Chrome update put me on version 122.0.6261.58.

[skjnldsv]

Worked too! Thanks @mohamad68 !

[jsodeman]

A note for those using Vue 3 and Vite, you can use this plugin or app instead:

https://devtools-next.vuejs.org/

[woodinteractive]

I also had to remove the "update on reload" check from the service workers, then it started working.

That seems to be it. Disabling it makes the vue dev tools appear. Rechecking makes them disappear again.

This 100% fixed it for me.

[qroulland]

The solution of @urbgimtam works for me on MacOS Chrome 🙌🏻

[llemllen]

Worked remove 'update on reload'.
When Vue DevTools cannot be opened, it may cause some other extensions to fail to popup. Restarting the browser is required for them to popup again.

[juanhuerta]

@mohamad68 removing "update on reload" check worked for me, thanks!

[CameronSmithSPT]

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.
I can right-click on Vue DevTools and choose "Reload Frame" which saves me having to close and re-open the Developer Tools window completely. Still not ideal but it is faster.

[GuyGeva93]

Hello, is there any update? Does the newest version work?

[jsodeman]

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.

[irfanfadilah]

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.

[xiaoxustudio]

I had the same problem on Edge browser, react devtool will add options here, but vue devtool can't find any entry.

react devtools

vue devtools

[duduindo]

Unchecking the Service Workers' "Update on reload" worked for me too.

[xiaoxustudio]

I had the same problem on Edge browser, react devtool will add options here, but vue devtool can't find any entry.

react devtools vue devtools

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

[okaufmann]

Unchecking the Service Workers' "Update on reload" worked for me too.

Worked for me too

[urbgimtam]

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:

Uncaught Error: Dynamic require of "crypto" is not supported

Anyone found out more?

[Dual-Ice]

Unchecking the Service Workers' "Update on reload" worked for me too.
But tools behaves strange and sometimes couldn't shows updated information

[jankrnavek]

The same problem with VueDevTools 6.6.1
Unchecking the Service Workers' "Update on Reload" doesn`t work for me as well.
Reinstallation of Brave had not effect too...

Windows 11
Brave [Version 1.64.109 Chromium: 123.0.6312.58 (Official Build) (64-bit)]

Tested on Nuxt 3.11, Vue 3.4.21 apps...

[urbgimtam]

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.
Updating the project to Nuxt v3.11/Vue 3.4.21 without closing the Chrome DevTools allowed to use it without problems.
As soon as I closed and reopened the Chrome Devtools, Vue Devtools doesn't show anymore.

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?

[urbgimtam]

Downgrading nuxt devtools to 1.8.0 seems to allow VueDevtools to work again. nuxt/devtools#634

[Dual-Ice]

Also vue-devtools can be downgraded to 5.6, but for me it isn't comfortable

[luanhenzo]

Downgrading nuxt devtools to 1.8.0 seems to allow VueDevtools to work again. nuxt/devtools#634

Thanks. Disabling Nuxt Devtools made Vue Devtools panel appear again.

[sed9xa]

This worked perfectly fine for me
I think there is something with nuxt devtools version.

[didaquis]

I have same problem on macOS using Chrome.

[luanhenzo]

Fixed in @nuxt/devtools 1.1.5.

[KaskoYurii]

The same issue:
Since the latest 2-3 Chrome updates.
Chrome:
Version 123.0.6312.87 (Official Build) (arm64)
DevTools:
Version
6.6.1
macOS Sonoma
Version 14.4.1

Don’t have any other devtools.

[j-chronogram]

Thanks. Disabling Nuxt Devtools made Vue Devtools panel appear again.

This worked for me as well, thank you!