A visual editor for Vite with nothing to install

Correct, for Vite. The plugin is compiled into the PortBay binary, written out to PortBay's own data directory, and handed to your dev server through a generated config that lives outside your repo. There is no package to add and none to remove: uninstall PortBay and your package.json, node_modules and config files are byte-for-byte what they were. The plugin is not on npm and never will be, because nothing needs to serve it.

Vue, Svelte and SvelteKit, React (which is also the lane Preact and Solid take), Qwik and Angular — anything running on Vite. Astro and Nuxt are supported too, through their own injection paths, because neither takes the same config flag: Astro needs a project-relative config path and Nuxt has no --config at all, so it is extended as a layer instead. Each of those has its own page with the details specific to it; this page covers the mechanism they share.

JSX was refused, and that changed in August 2026. Documentation and older write-ups still say .jsx and .tsx cannot be stamped; that is out of date. Both are scanned script-first now and their host elements carry data-pb-loc, and a className edit writes back through a tree-sitter JSX path. One tier genuinely did not come back — see the next answer.

Component usages. In a .vue or .svelte file, a <Card/> tag carries its own coordinate, so an element a component rendered still traces back to your markup. In a .jsx or .tsx file it does not, because a capitalised tag there can be a TypeScript generic parameter list rather than a component, and inserting an attribute into the wrong one is a syntax error in your module. The practical loss is markup produced by a library you did not author: it carries no coordinate.

No. The plugin declares apply: 'serve', so Vite loads it for the dev server and never for vite build. There is also nothing to leave behind in your source, because the attribute is added during serving rather than written into your files — the difference from editors that write their own id attributes into your components and expect you to strip them later.

No. PortBay can only add its own instrumentation to dev servers it launches through Vite or Astro, so Babel pipelines get no stamping. Text, class and attribute edits still resolve by searching your source, but structural edits are refused rather than guessed. If you are on Next.js, that has its own supported path through an SWC plugin.

Two capabilities are worth knowing about. Renaming a Tailwind design token rewrites every reference to it across the project in the same save, so the definition and its uses never drift apart. And a selection can be extracted into a new component, which is supported on Astro, JSX, Svelte and Vue — the four languages whose grammar PortBay can move a subtree in safely. It refuses by name when a selection contains a template expression it cannot move rather than producing something that does not compile.

No. It is a Pro feature, still in early access behind an opt-in toggle in Settings, and it is not compiled into the open-source build. The rest of what this page describes — running your Vite dev server, the .test hostname, trusted HTTPS, the task board — is in the free, open-source app.