Skip to content
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

vite-plugin-checker-error-overlay custom element is shown as a separate root component in Vue Devtools #466

Open
2 tasks done
jiikoosol opened this issue Mar 3, 2025 · 0 comments

Comments

@jiikoosol
Copy link

jiikoosol commented Mar 3, 2025

Describe the bug

I'm not entirely sure if this is a bug or intended to be like this, but after upgrading vite-plugin-checker to version 0.9.0 I started seeing the custom element "vite-plugin-checker-error-overlay" in Vue Devtools as a separate root component. When developing, if you have to refresh the page several times, you also have to select the right component from Devtools, instead of the component being developed being directly visible in the tool, as it normally is. This causes multiple extra clicks which is really frustrating.

Tested with following Vue & Vite versions:

"vue": "^3.5.13",   
"vite": "^6.2.0"

Reproduction

  1. Update vite-plugin-checker to version 0.9.0
  2. Start your application and open Vue devtools
  3. See that there's a "VueElement" root component shown in "Components" tab

Image
Image

Expected behavior

Vue Devtools should ignore the vite-plugin-checker-error-overlay component as in version 0.8.0:

Image

System Info

System:
    OS: macOS 15.3.1
    CPU: (12) arm64 Apple M3 Pro
    Memory: 548.77 MB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.14.0 - ~/.nvm/versions/node/v20.14.0/bin/node
    npm: 10.9.0 - ~/.nvm/versions/node/v20.14.0/bin/npm
  Browsers:
    Chrome: 133.0.6943.142
    Safari: 18.3
  npmPackages:
    vite-plugin-checker: ^0.9.0 => 0.9.0

Additional context

No response

Validations

  • Read the docs.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant