feat(dev-server): /@ng/component endpoint + HMR runtime bus (#145) - #186
Merged
lukekania merged 2 commits intoJun 9, 2026
Merged
Conversation
First slice of Hot Module Replacement: read the `hmr` flag and hot-swap
global stylesheets in place without a full page reload.
- project-resolver: parse `architect.serve.options.hmr` (base + active
serve configuration override) into `ResolvedAngularProject.hmr`;
defaults to false.
- cli: add `--hmr` / `--no-hmr` to `serve` (CLI wins over angular.json,
else inherit, else false). When HMR is on and a rebuild touches only
global stylesheet entries, emit a CSS-update instead of a reload.
- dev-server: new `DevServerEvent::CssUpdate { timestamp }` →
`event: css-update` SSE frame; the injected client swaps the
`styles.css` <link> with a cache-busted href, preserving page state.
Component template/style HMR and the `/@ng/component` update endpoint
land in follow-up slices on the milestone branch.
Runtime scaffolding for component-level HMR, ahead of the compiler
codegen that populates it.
- dev-server: new `DevServerEvent::ComponentUpdate { id, timestamp }` →
`event: angular:component-update` SSE frame; a shared `ComponentUpdates`
registry (id → update-module source) on `DevServerConfig`, served at
`GET /@ng/component?c=<id>` (text/javascript, empty 200 for unknown ids,
400 when `c` is absent) — mirrors @angular/build's component middleware.
- client: the injected script publishes a `window.__ngcHmr` bus and
dispatches `angular:component-update` to registered handlers; new
`HMR_RUNTIME_PRELUDE` binds `import.meta.hot` to that bus.
- serve: share the registry with the dev server and prepend the runtime
prelude to `main.js` on each HMR build so per-component initializers can
resolve `import.meta.hot`.
The registry stays empty and component edits still trigger a full reload
until the template-compiler emits update modules (next slice).
lukekania
changed the base branch from
feat/hmr-config-css-swap
to
milestone/v0.11.0-builder-parity
June 9, 2026 14:09
This was referenced Jun 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Runtime scaffolding for component-level HMR (#145), ahead of the compiler codegen that populates it. Stacked on #185.
Changes
DevServerEvent::ComponentUpdate { id, timestamp }→event: angular:component-updateSSE frame; a sharedComponentUpdatesregistry (id → update-module source) onDevServerConfig, served atGET /@ng/component?c=<id>(text/javascript, empty200for unknown ids,400whencis absent) — mirrors@angular/build's component middleware.window.__ngcHmrbus and dispatchesangular:component-updateto registered handlers; newHMR_RUNTIME_PRELUDEbindsimport.meta.hotto that bus.import.meta.hot.Scope
The registry stays empty and component edits still trigger a full reload until the template-compiler emits update modules (next slice, stacked on this branch).
Tests
angular:component-updateSSE frame shape;query_paramraw-encoded extraction;/@ng/componentendpoint (registered id → module, unknown → empty 200, missingc→ 400); client exposes the__ngcHmrbus + prelude.Targets the milestone branch via the stack; retarget to it once #185 merges.