One Remix route holds the markup and the head — edit both

By any dependency whose name starts with @remix-run/ in your package.json. That covers every package in the family rather than one specific entry point, so a project that depends on @remix-run/node and @remix-run/react but not on a meta-package is still recognised.

Not if your Remix app runs on Vite, which every current scaffold does. PortBay launches the dev server, so it hands Vite a generated config that imports and spreads your own and adds a source-location plugin carried inside the app itself. Your package.json, lockfile and vite.config stay byte-identical, and there is no package to add or remove.

An older Remix app drops to the text-matching lane. A Remix project without React and Vite in package.json gives PortBay no dev-server seam to instrument, so text, class and attribute edits resolve by searching your source instead of by following a coordinate, and structural edits are refused rather than guessed. Moving that project onto Vite is what turns precise mapping back on — there is nothing to install either way.

Into that route's own meta export, in the same file as the markup you were just editing. Remix renders a route's meta into exactly that route's head and nothing else's, so the value cannot leak onto another page. PortBay reads the array whether it is written as an arrow function, a concise arrow body or a function declaration, and if a field is missing it adds a descriptor to the array rather than declining.

Component usages. Route modules are .tsx, which is a script-first file, so the host elements you wrote carry coordinates but a <Card /> tag does not. The practical consequence is that markup produced by a component you did not author — a UI library's own internals — has no coordinate. The reason is specific to the file type: in a .tsx a capitalised tag can be a TypeScript generic parameter list, and inserting an attribute into the wrong one would be a syntax error in your module.

Both. A className edit on a .tsx goes through a tree-sitter path that rewrites the attribute in place rather than a text replacement, and the right-hand rail covers layout, spacing, size, position, typography, backgrounds, borders and effects. Text is edited by double-clicking it in the live page rather than typing into a panel field.

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 the Remix dev server on a real .test domain with trusted HTTPS is in the free app.

Yes. JSX and TSX are among the four formats where that structural edit is supported, so an element inside a route module can be moved into a new component file, with the import added to the route and the original span replaced by the tag. It refuses, by name, any span carrying a template expression — a value that was a local in the route would not exist in the new file, and the extraction would produce a module that no longer builds.