Comments (71)
@mohamad68 Thanks, that worked for me too.
I had it running in incognito mode, but even after unregistering all service workers, it still didn't work.
I also had to remove the "update on reload" check from the service workers, then it started working.
from devtools.
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)
from devtools.
Here are the steps that worked for me:
Update Chrome to the latest version.
Completely remove the previous Vue DevTools installation.
Install Vue DevTools version 6.6.1.
Right-click on the Vue DevTools icon at the top and select 'Inspect popup,' then proceed to clear all storage applications
from devtools.
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.
from devtools.
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.
from devtools.
Unchecking the Service Workers' "Update on reload" worked for me too.
from devtools.
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
from devtools.
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.
from devtools.
me also - since 14 Feb v6.6.0.
Broken?
from devtools.
Also here. Looks like something was broken after the last update (14/2)
from devtools.
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.
from devtools.
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
from devtools.
Looks like something is wrong with the service worker (Manifest V3) :(
from devtools.
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.
from devtools.
Maybe it's somehow caused by the migration to Manifest V3...
from devtools.
Maybe try exporting your bookmarks and reseting the Chrome profile
from devtools.
@Akryum That's not really acceptable imho. I have many other extensions using manifest v3 :)
Please note that the extension DOES show up in the toolbar, and the logo is green.
But clicking on it does not show the usual Vue is detected
, it does nothing.
I think this is really a problem with the extension itself
from devtools.
I also got it working after following the steps by @mohamad68 and @urbgimtam. The Chrome update put me on version 122.0.6261.58.
from devtools.
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.
from devtools.
I've disabled the latest version and reinstalled the legacy version which seems to be working for now - Legacy v5
from devtools.
I'm having the same issue on mac and chrome
from devtools.
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
from devtools.
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.
from devtools.
i followed @mohamad68 which did not work but after following @urbgimtam it started working, thanks everyone
from devtools.
Downgrading nuxt devtools to 1.8.0 seems to allow VueDevtools to work again. nuxt/devtools#634
from devtools.
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
from devtools.
@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
from devtools.
It's not a matter of it being acceptable, it's all about trying to find the cause of the issue. This is all made extra difficult because I can't reproduce it myself and neither can a lot of people.
from devtools.
@vogtm Those warnings can be safely ignored
from devtools.
After trying more stuff yesterday evening I have found nothing obvious.
But to summarize my observations:
It works in newly created chrome profiles.
It works in incognito tabs
It works in "broken" profiles when:
- open your page with vue code (e.g. localhost:8080)
- open chrome devtools (β β₯ i )
- with the chrome devtools in focus open the chrome devtools for the chrome devtools (β β₯ i ) -> I call them internal devtools in the next step
- with the internal devtool in focus refresh (β r) -> a new normal tab opens with devtools://devtools/bundled/device_mode_emulation_frame.html?...
- the (normal) chrome devtools also reload and the vue devtools show up and are useable
(Maybe someone with the bug can check if they can reproduce the steps above with the same results)
My assumption would be similar to @woodinteractive that there is a weird chrome caching / extension thing going on.
Are there other extensions that recently shown the same problems? Maybe there are people from the chrome devtools team we can reach out to that might have a rough idea what could be the problem? By now, it seems more like a chrome bug to me than a vue devtool bug.
Update on the "do other extensions experience something like this":
sveltejs/svelte-devtools#184
from devtools.
Worked too! Thanks @mohamad68 !
from devtools.
Unchecking the Service Workers' "Update on reload" worked for me too.
Worked for me too
from devtools.
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.
from devtools.
I can't reproduce with the provided repo on Chrome/Linux.
from devtools.
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.
from devtools.
@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
from devtools.
Can you try:
- restarting chrome
- restarting the computer
- another browser such as Firefox or Edge
and report back?
from devtools.
from devtools.
Check that the extension has 'Site access' setting set to 'On all sites':
from devtools.
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':
from devtools.
Does it work in edge?
from devtools.
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
Brave:
from devtools.
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.
from devtools.
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.
from devtools.
Hey guys, it seems that FORCE REFRESH can be helpful. My setps are:
- closing the chrome developer tools,
- FORCE REFRESH (Ctrl + F5 or Ctrl + Shift + F5 depends on your setting) the page,
- 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.
from devtools.
vue-dev tools not working any more
from devtools.
Maybe you can try to create a new profile.
Could anyone also try to right-click in the blank extension drop-down and paste the console content?
from devtools.
All right I was faffing around a bit - same train of thought.
With the chrome devtools for the devtools open, and reloading it with 'cmd r' the vue devtools show up and the console logs:
Edit: oh, when then clicking on the vue devtools tab, it will open propperly and the devtools devtools will show another warning:
from devtools.
Maybe you can try to create a new profile.
Could anyone also try to right-click in the blank extension drop-down and paste the console content?
Tried it, and - at least for me - it seemed to work after installing the vue devtools on that profile.
Also the errors above does not appear with the new profile.
Will investigate further
from devtools.
I tried my laptop and devtools is working on it, but not on my desktop. Both are running the same version of Chrome, both on up to date Windows 11, both signed into the same Google account. Same code, same version of node.
from devtools.
I work in a team with three other developers. All of us are using the same computers, the same version of OS, the same browsers (same version, Chrome Version 121.0.6167.184 (Official Build) (arm64)), and the same projects from the same repo. They aren't having any issues with the extension whereas I am.
I installed the DevTools extension on Firefox and was able to get it to load, however, it wouldn't register Pinia. This feels like a cache issue related to the browser at the OS level or something beyond my ability to diagnose.
from devtools.
It's not a matter of it being acceptable, it's all about trying to find the cause of the issue.
Sorry, should I been more clear π
The bug is fine, it happens! What is not acceptable is "creating a new profile" as a workaround imho :)
from devtools.
A note for those using Vue 3 and Vite, you can use this plugin or app instead:
https://devtools-next.vuejs.org/
from devtools.
The solution of @urbgimtam works for me on MacOS Chrome ππ»
from devtools.
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.
from devtools.
@mohamad68 removing "update on reload" check worked for me, thanks!
from devtools.
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.
from devtools.
Hello, is there any update? Does the newest version work?
from devtools.
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.
from devtools.
I had the same problem on Edge browser, react devtool will add options here, but vue devtool can't find any entry.
from devtools.
I had the same problem on Edge browser, react devtool will add options here, but vue devtool can't find any entry.
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
from devtools.
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?
from devtools.
Unchecking the Service Workers' "Update on reload" worked for me too.
But tools behaves strange and sometimes couldn't shows updated information
from devtools.
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...
from devtools.
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?
from devtools.
Also vue-devtools can be downgraded to 5.6, but for me it isn't comfortable
from devtools.
This worked perfectly fine for me
I think there is something with nuxt devtools version.
from devtools.
I have same problem on macOS using Chrome.
from devtools.
Fixed in @nuxt/devtools 1.1.5.
from devtools.
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.
from devtools.
Thanks. Disabling Nuxt Devtools made Vue Devtools panel appear again.
This worked for me as well, thank you!
from devtools.
Related Issues (20)
- Freezing Microsoft Edge
- The extension conflicts with walutomat.pl (the site is broken when the extension is enabled) HOT 1
- state, render, currentRoute errors in console HOT 3
- Component graph doesn't show custom renderer components
- Vue Devtools' detector-exec.js in combination with Cookiebot prevents DOMContentLoaded event?
- Performance tab: Wrong timing shown on group
- Devtools Gets "Stuck", Doesn't Refresh on Browser Refresh HOT 12
- Unable to view event details in timeline
- Some component does not show the props panel. HOT 2
- Component State Not Updating HOT 3
- Cannot view AForm(from ant-design-vue) components details, showed me 'Select A Component'
- If the base option is configured for Vite, open in editor will fail
- no funciona HOT 2
- README: Mention and link to devtools-next
- Multiple Vue apps mounted cause empty devtools on Chrome HOT 3
- Quickly open the closest parent component that can be opened in the editor.
- It is suspected that vue-devtools causes chrome memory overflow and then crashes HOT 8
- Vue3 chrome devtool not working when vite-plugin-vue-devtools node module is enabled HOT 1
- [PSA] Devtools Next for Vue 3 + Vite users HOT 1
- Pages: mishandling of navigation routes with regex pattern matching HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from devtools.