Qwik City routes, edited down to the line of .tsx

No. The default Qwik scaffold ships a direct Vite devDependency and a real root vite.config.ts, which is the seam PortBay needs. It launches your dev server with a generated config that imports and spreads your own and adds a source-location plugin carried inside the app itself. Nothing is written into your repo and there is no package to add — your package.json, lockfile and vite.config stay byte-identical.

Then it drops to the text-matching lane. A project exposing neither a vite dependency nor a vite.config gives PortBay no dev server it can reach, so text, class and attribute edits resolve by searching your source rather than by following a coordinate, and structural edits are refused rather than guessed. The default scaffold ships both, so this is the unusual case rather than the normal one.

Component usages. Route files are .tsx, a script-first format, so the host elements you wrote carry coordinates but a <Hero /> tag does not. Your own components are still fine — the elements inside them are stamped at their own lines in their own files. What genuinely has no coordinate is markup produced by a package you did not author. The reason is grammatical: a capitalised tag in a .tsx can be a TypeScript generic parameter list, and inserting an attribute into the wrong one is a syntax error in your module.

Through the route's exported DocumentHead object literal. Qwik City reads that export for exactly that route and nothing else's, so a value written there cannot leak onto another page. An absent field is inserted rather than refused — as a new key on the existing object, or as a brand-new export const head appended to the route when it has none at all.

The edit bar boots in Preview mode, where the page and your event handlers behave exactly as they normally do, and switching to Edit changes what your clicks mean rather than what the app is. More importantly, the edit is written to your source file, so what you get afterwards is the same app rebuilt from changed source — not a runtime patch layered over a running page.

No. The plugin declares apply: 'serve', so Vite loads it for the dev server and never for a build. There is nothing to leave behind in your source either, because the attribute is added while the file is served rather than written into it — the difference from editors that insert their own id attributes into your components and expect you to remove them before shipping.

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. It also refuses to run while the project is shared over a public tunnel, and the edit bar works only on local .test hosts. Running Qwik on a real .test domain with trusted HTTPS is in the free, open-source app.

Yes. JSX and TSX are among the four formats where that structural edit is supported, so an element in a route file can be moved into a new component file, its import added, and the span it vacated replaced by the tag. The one deliberate refusal is a span carrying a template expression, which is named rather than attempted — the values it closes over are locals of the route and would not exist in the new file.