Angular templates, edited by markup match — and what it refuses

By @angular/core in your package.json dependencies. That is the whole signal — no config file to add, no framework field to set, and no directory scan. Everything downstream, including which write lane the project gets and where its page title lives, follows from that one detection.

No, and this is the honest limit of the Angular lane. PortBay adds source-location stamping only to dev servers it launches itself through Vite or Astro, and the Angular CLI's builder is neither. So an Angular element carries no data-pb-loc, and edits are resolved by finding that markup in your template files instead of by following a coordinate. PortBay tells you which mode a project is in rather than degrading quietly.

Text, class and attribute edits, plus page settings — all four write lanes. That is tested rather than claimed: PortBay's cross-stack guard builds a real Angular fixture project, drives each lane against it, and reads the changed bytes back off disk from src/app/app.component.html. A lane that quietly did nothing is the exact failure that test exists to catch, so a silent no-op cannot ship.

Three things, all for the same reason — the value you see is not in the file. A class bound with [class] or [ngClass] is computed from a component field, so there is no class name in the template to change. Interpolated text inside {{ }} came from your data. And structural edits — moving, wrapping or converting an element — are refused rather than guessed, because without a coordinate there is no way to be sure which occurrence you meant.

Into src/index.html. Angular is unusual among the frameworks here in having a genuinely static document shell: src/index.html really is the head every route renders through, so patching it takes effect rather than being overwritten on the next render. PortBay reports it as site scope in the panel, so you can see that a title written there applies to every route rather than to the one you happen to be looking at.

Only where the markup is yours. A library's own internal template is not in your source tree, so there is nothing to match and PortBay says so rather than editing something else. Attributes and classes you put on the library's component in your own template are in your file and do resolve normally.

PortBay's visual editor is free — the bar and the edits you make with it ship to everyone, with no plan and no opt-in. What Pro buys is publishing to production. It is still not compiled into the open-source build. It refuses to run while the project is shared over a public tunnel — stop the share first — and the edit bar works only on local .test hosts. Running your Angular dev server on a real .test domain with trusted HTTPS is free.