4grayandClaude Opus 5.5 d88d005062 perf(web): run the renderer zoneless and drop the zone.js polyfill ...

Plan item C6 step 5. app.config.ts provides
provideZonelessChangeDetection() directly and apps/web builds without the
zone.js polyfill, so a tick runs only when a signal, markForCheck, an
Angular event or a render hook asks for one, not after every macrotask.
The flag from #1824 (change-detection.providers*.ts and the *-zoneless
configurations) goes away; a build-config test fails if the polyfill or a
zone provider comes back.

NgZone.run/runOutsideAngular calls that only mattered with zone.js are
removed from the dashboard data services, the settings unload guard and
the embedded MPV position poll (with the spec case asserting it), and
the unused polyfills.ts, polyfills-test.ts and setup-jest.ts are deleted.
Unit tests keep zone.js/testing for fakeAsync and waitForAsync;
apps/remote-control-web still bootstraps with zone.js.

renderer.initialBytes: 1,596,201 -> 1,545,931 bytes (-50,270) on a local
production build of this base; the baseline is lowered to the measured
value.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-13 08:44:52 +02:00

..

architecture

perf(web): run the renderer zoneless and drop the zone.js polyfill

2026-10-13 08:44:52 +02:00

development

fix(portals): resolve cancelled and 401/403 portal requests instead of rejecting through IPC (#1861)

2026-10-10 11:28:59 +02:00

maintenance

perf(tooling): compositing probe, report command and route-wide clip-mask guard (#1858)

2026-10-09 21:34:57 +02:00

superpowers

refactor(storage): seams for server-backed playlist storage (#1896)

2026-10-11 20:03:58 +02:00