Compatibility
Everything the plugin needs from your toolchain and browsers, on one page.
Version ranges come from package.json; the rest from what the runtime does.
Toolchain
Section titled “Toolchain”| Requirement | Range | Note |
|---|---|---|
| Node | >= 20 |
Runtime engine of the published package |
| Vite | ^7.0.0 || ^8.0.0 |
Peer dependency |
| Lit | ^3.0.0 |
Peer dependency |
| TypeScript | any recent version | Decorator settings below decide what can be patched in place |
Reactive properties must be declared one of two ways for in-place patching to
work: experimental decorators, with experimentalDecorators: true and
useDefineForClassFields: false, or static properties. Standard accessor
decorators are detected and fall back to a reload.
Optional peers
Section titled “Optional peers”Each one is imported only on the path that needs it, so the plugin installs and runs without any of them.
| Package | Range | Unlocks |
|---|---|---|
lightningcss |
^1.30 |
Lightning CSS processing of css template literals |
@vitejs/devtools-kit |
^0.7.5 |
Mounting the Lit panel into the Vite DevTools hub |
cac |
^7 |
The lit-devtools command |
@devframes/agentic |
1.0.0 |
lit-devtools mcp, the stdio bridge for coding agents |
astro |
^7.3 |
The Astro integration, @oddsquad/vite-plugin-lit/astro |
@lit-labs/ssr |
^4.1 |
Its renderer, which renders Lit on the server |
@lit-labs/ssr-client |
^1.1.8 |
Its renderer’s hydration in the browser |
The panel also needs @vitejs/devtools active in the same Vite config, which is
what serves the DevTools overlay the panel docks into.
Browsers
Section titled “Browsers”?css-sheet, urlSheet(), and the inline build modes all produce a constructed
CSSStyleSheet, so they need constructable stylesheet support.
| Browser | Minimum |
|---|---|
| 73 | |
| 101 | |
| 16.4 |
Importing a sheet module throws in jsdom, which can’t construct a
CSSStyleSheet. Node has none at all; there, as in a server render with
@lit-labs/ssr, the module builds a stand-in that carries the css text, and
Lit’s server renderer writes it into the page.
Editors
Section titled “Editors”sourceOverlay.editor accepts these built-in keys, and an unknown name falls
back to VS Code. A {name, url} object supplies your own URL builder.
| Key | Editor |
|---|---|
vscode |
VS Code |
cursor |
Cursor |
zed |
Zed |
idea |
IntelliJ |
windsurf |
Windsurf |
Not supported
Section titled “Not supported”The Rolldown full-bundle dev mode. The plugin targets the standard Vite dev server pipeline, which serves and re-executes modules one at a time.
Contributing to the plugin itself needs Node 26 and pnpm 12; see Development.