Loads of Vue warns with 6.6.0

[bobvandevijver]

Vue devtools version

6.6.0

Link to minimal reproduction

None

Steps to reproduce & screenshots

What is expected?

No errors. Seems that for each component state, render & currentRoute are accessed while not being defined on that particular component, causing the vue warn handler to kick in.

What is actually happening?

A load of warnings are printed, filling the complete console output.

System Info

System:
    OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
    CPU: (8) x64 QEMU Virtual CPU version 2.5+
    Memory: 8.93 GB / 15.62 GB
    Container: Yes
    Shell: 5.2.15 - /bin/bash
  Binaries:
    Node: 20.11.1 - /usr/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 10.2.4 - /usr/bin/npm
  npmPackages:
    vue: 2.6.14 => 2.6.14

  System:
    OS: Windows 11 10.0.22631
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
    Memory: 7.25 GB / 31.68 GB
  Binaries:
    Node: 20.11.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.21 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (121.0.2277.112)
    Internet Explorer: 11.0.22621.1

Any additional comments?

This started this morning, so with the 6.6.0 update.

I do not have a usable repro yet.

[bobvandevijver]

It seems to happen when the page you're working is being reloaded: the extension does not pick up this reload at all (old components and values are still being shown, and it is no longer possible to navigate at all). When reopening the Edge devtools (which seems to restarts the vueks/devtools) the errors start for me.

I strongly suspect this is related to the reload behaviour, which is reproducible on https://sfc.vuejs.org/. Steps:

• Open the playground
• Open the devtools
• See the value of the msg ref change when typing in the default input field
• Refresh the page
• vuejs/devtools is no longer connected to the page being shown, navigation doesn't do anything, values are not updated etc.
• Reopening the complete devtools and with it the vuejs/devtools solve the issue