bug: DevTools icon pulses infinitely with vite-plus lazyPlugins in http://localhost:5173/__devtools__/

Open
#1,153 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
typescript, vite
Domain
devtools, frontend

Research direction

Start by reproducing the infinite pulse at /devtools/ with the reported vite-plus lazyPlugins configuration and the plugin appended to resources/js/app.ts. Trace why the websocket connection and dashboard mount do not complete; done means the icon stops pulsing, the connection succeeds, and the dashboard panel mounts.

Written by the indexing model from the issue text.

Description

The floating Vue DevTools icon appears on the webpage but pulses infinitely. It fails to establish a websocket connection or mount the dashboard panel. Latest updates for Laravel Starter kit.

  • Operating System: Windows 11 ( VS Code)
  • laravel/installer 5.32.0
  • vite-plus 0.3.0
  • vite 8.3.2
  • Laravel Version: 13.x
  • Inertia Version: 3.x
  • Vue Version: 3.5.x
  • Bundler: Vite (via vite-plus wrapper)
  • Plugin Version: vite-plugin-vue-devtools (Latest)
import { defineConfig, lazyPlugins } from "vite-plus";
import vueDevTools from "vite-plugin-vue-devtools";

export default defineConfig({
    devtools: {
        apply: "serve",
    },
    plugins: lazyPlugins(() => [
        vueDevTools({
            appendTo: "resources/js/app.ts",
        }),
Dominant language
TypeScript
Stars
2.9k
Forks
292
Avg merge
3d 22h
Merged PRs (30d)
29

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vuejs/devtools

All issues in vuejs/devtools

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.