)

Editing a component `templateUrl` `.html` put a `full-reload` on the HMR
socket on top of the `angular:component-update` that already hot-swapped
the template.

`handleHotUpdate` returned `ctx.modules` for the template, and that array
is empty: the file was watched but never a module. Vite full-reloads any
changed `.html` whose module list is empty or holds no `js` module.

Vite's client usually drops that payload, because an `.html` path only
reloads when it matches `location.pathname`. That guard is gone when the
path is `*`, which is what Vite sends in `middlewareMode` — so the page
reloaded right after the update was applied. Reproduced at the reporter's
versions (0.0.35 / vite 8.2.1 / angular 21.2.21): `middlewareMode`
reloads, plain SPA does not, `.css` never does. Either way the terminal
printed `page reload …` and cleared the screen on every save.

Register each template with `addWatchFile`, so it enters the module graph
as a `js` module with the component `.ts` as its importer, and return it
as its own HMR boundary. The browser never imported the template, so the
resulting `js-update` is a client no-op; the DOM change still comes from
`angular:component-update`.

Templates only. An import edge on a style makes Vite propagate the change
up to the component `.ts` and re-execute it, which defines a duplicate
class (NG0912) and leaves `angular:component-update` patching a class that
is no longer mounted — styles then go stale from the second edit onward.
Styles never needed it: Vite only force-reloads on `.html`.

The e2e sentinel tests could not catch this. They assert the browser did
not act on a reload, which stayed true while the server kept asking for
one. Added `captureWirePayloads`, which records the HMR socket across
navigations, and two tests: a template edit sends no `full-reload`, and
`index.html` still does.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FUvBViRkyuDvqUMkuT5XnH

`{ id, _clientModule: { isSelfAccepting: false } }` is not assignable to
`Partial<ModuleNode>` — `_clientModule` is an `EnvironmentModuleNode`.
CI's Lint step failed on it, before the e2e suite ran.

Extract `createMockTemplateModule`, which casts once and hands back the
client node so the assertion stays readable.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FUvBViRkyuDvqUMkuT5XnH

Vite sets `mod.file` to `cleanUrl(mod.id)`, so a template that application
code also imports as `./tpl.html?raw` is filed under the same path and lands
in `ctx.modules` next to the node `addWatchFile` created. Matching on `file`
marked that browser-imported variant as a boundary too, and Vite then stopped
propagation at a module with no `import.meta.hot.accept` handler — its
importers kept the stale raw string.

Match on `id` instead. An exact match means same file, no postfix, so it
covers `#fragment` as well as `?query`.

Measured on an Angular app whose non-component module imports the same file
as `./app.html?raw`:

  before   raw value after a template edit: MARKER_V0  (stale)
  after    raw value after a template edit: MARKER_V1_EDITED

#443 stays fixed — no `full-reload` in SPA or middlewareMode when nothing
imports the template. With a `?raw` importer present the page reloads again,
which is Vite's native semantics for a chain with no accept boundary, and is
what keeps the raw importer correct.

Reported by Codex review on #444.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FUvBViRkyuDvqUMkuT5XnH

With `liveReload: false`, `handleHotUpdate` returns on its first line, so
the graph edge has no consumer inside the plugin. It still fed Vite's
default propagation, which found no accepting boundary and issued a full
reload — turning a payload the client used to drop into an unconditional
one with path `*`.

Measured on an Angular app at `liveReload: false`, editing a template:

  build   mode   payload                                    navs
  main    SPA    full-reload path=/src/app/app.html          0
  PR      SPA    full-reload path=*                          1   <- regression
  gated   SPA    full-reload path=/src/app/app.html          0
  main    MW     full-reload path=*                          1
  gated   MW     full-reload path=*                          1

The gate restores main's payloads exactly, and `liveReload: true` is
unaffected — no `full-reload` in either mode, template still self-accepting.

Also collapse the duplicated plugin lookup in the test file into
`getAngularPlugin(options)` rather than add two more copies.

Reported by Codex review on #444.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FUvBViRkyuDvqUMkuT5XnH