vitejs

devtools

DevTools Framework for the Vite Ecosystem.

by vitejs

TypeScript

TypeScript56.1%
Vue41.5%
JavaScript0.9%
CSS0.7%
MDX0.6%
HTML0.1%

Commit activity

Last 12 weeks · 101 commits

Full graph →

Community health

5 of 6 standards met

Community profile →
87
✓README✓License✓Contributing✓Code of Conduct○Issue Template✓PR Template

Recent PRs & issues

Active · Last activity 4h ago
See all on GitHub →
arkadiusz-swierczek-pm

Describe the bug Follow-up to vitejs/devtools#554. After the fix, the root redirect and the DevTools SPA itself resolve correctly under a deploy base, but the URLs baked into the emitted manifests and RPC dumps are still root-absolute, so every sub-panel 404s. Reproduction Clone https://github.com/arkadiusz-swierczek-pm/vite-devtools-static-output-subpath; npm ci; npm run build -- --base /ci-build-123456/; node server.ts System Info Used Package Manager npm Validations [x] Follow our Code of Conduct [x] Read the Contributing Guide. [x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. [x] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead. [x] The provided reproduction is a minimal reproducible of the bug.

arkadiusz-swierczek-pm · 18h ago
0froq

Description Pass Vite's to as . Static snapshots now rebase frame bases, dock URLs, and the absolute asset references inside copied SPAs, so output served below the domain root works end to end. Bump to , the first release with the option. The option itself comes from devframes/devframe#494. Draft until that release is on npm. Linked Issues Fixes #583 Test The reproduction from #583 with the hub fix applied locally: , then serve at that path. The viewer, the rolldown panel, the messages and inspect panels, the chunks, and the assets all return 200. A scan of the baked URLs finds no root-absolute leftovers. No new automated test here. The rebasing lives in and is covered by its build tests, and this PR forwards the option.

0froq · 18h ago
CaiPeng1989

Describe the bug Opening the Oxc panel in Vite DevTools fails with when is unreachable from the Node process running / . The Overview RPC () does an unconditional remote fetch for latest-version comparison. If that request fails, the whole overview query fails and the panel cannot load — even though local Oxlint / Oxfmt (including Vite+ bundled versions) are available. Reproduction 1. Install + and enable . 2. Block or fail access from Node to (common with browser-only VPN / split tunneling / restricted networks). 3. Run / and open the Oxc dock panel. Expected Overview should still render local toolchain info. Latest-version comparison should be best-effort and skipped on network failure. Actual Panel shows . Relevant code In Overview RPC: There is no around this call. Suggested fix Wrap the fetch in (and check ). On failure, continue with local version info and skip / mark unknown the "latest" comparison. Environment Vite via Vite+ () Windows 10, Node 22+ Browser can open , but Node/ process could not at the time of failure (VPN split tunneling)

CaiPeng1989 · 8h ago
zerone0x

Description The RPC fetched the latest Oxlint/Oxfmt versions from with no error handling. When Node can't reach that host (VPN split tunneling, restricted networks), the whole overview rejects and the Oxc panel shows , even though local Oxlint/Oxfmt info is available. This PR makes the latest-version lookup best-effort: New helper: 5s timeout (), check, and a . It also validates the payload shape. On any failure it returns versions. is now . means the latest version is unknown, and it is never treated as outdated. In the overview page, the "Latest" / "Update Available" badge is hidden when is unknown, so there's no false "Update Available". Version, links and tool views still render as before. Linked Issues Fixes #626 Additional context Added , which covers the success path, a rejected fetch, a non-OK response, and the overview still reporting local versions when the lookup fails. These tests fail on and pass with this change. Ran locally: , , (55 files / 407 tests passed), and .

zerone0x · 8h ago
SaKaNa-Y

Describe the bug Settings → Shortcuts lets me assign shortcuts to Open in Editor and Open in Finder, but pressing either shortcut does nothing visible. The browser console reports: Both commands failed consistently when repeated. Cmd+K still opens the command palette normally. Reproduction Reproduced with the repository's core playground: 1. Start the playground with after setting up the repository. 2. Open the playground in Chrome and authorize Vite DevTools. 3. Go to Settings → Shortcuts. 4. Assign Ctrl+Shift+E to Open in Editor and Ctrl+Shift+Y to Open in Finder. 5. Close the shortcut editor, focus the host page, and press each shortcut. Neither action opens its target; both produce the error above. Each was repeated twice with the same result. This reproduction uses the existing playground rather than a separate reduced project. Expected behavior A shortcut offered in Settings should have a usable execution path. Could you clarify the intended behavior for these two commands: are they meant to support user-assigned shortcuts, and if so, where should the target path come from? Code observations and ownership The failing path crosses both repositories: Vite DevTools registers these two commands with a required and . Its RPC handlers resolve that path against the workspace root. The intended target of these Vite-specific commands belongs here. Devframe's owns the shortcut settings that offer these bindings and the keyboard dispatcher that calls without arguments. Handling commands that require arguments may therefore need a change upstream in Devframe. Filed here because this is reproducible in Vite DevTools with its built-in commands. Could you confirm the intended shortcut behavior and whether this issue should be transferred to ? These observations explain the missing-path error, but do not establish whether the intended resolution is to supply a target or restrict shortcut eligibility. System Info macOS, Chrome 153 Vite DevTools core playground; package version: 0.7.3 and : 0.9.18 Used Package Manager pnpm

SaKaNa-Y · 1d ago
Structured data for AI agents

Repository: vitejs/devtools. Description: DevTools Framework for the Vite Ecosystem. Stars: 1213, Forks: 98. Primary language: TypeScript. Languages: TypeScript (56.1%), Vue (41.5%), JavaScript (0.9%), CSS (0.7%), MDX (0.6%). License: MIT. Homepage: https://devtools.vite.dev/ Topics: devtools-kit, rolldown, vite, vite-devtools, vite-plus. Latest release: v0.8.3 (1d ago). Open PRs: 13, open issues: 20. Last activity: 4h ago. Community health: 87%. Top contributors: antfu, webfansplz, yuyinws, antfubot, SaKaNa-Y, liangmiQwQ, JianJroh, dvcolomban, arashsheyda, CoutinhoTTS and others.