I admit I’m not familiar with testing in Vue. In Angular, even though we encourage using the real router for tests, we still install a fake implementation of the browser platform APIs underneath so we’re not operating against the real history and location implementations.

03.03.2025 15:36 — 👍 0    🔁 0    💬 0    📌 0

Have you given much thought to the testing story? It’s really compelling to think about not needing to require app devs to only use FW APIs for navigation. With this though, we can mock the FW services to prevent real navs in jasmine/jets tests, updating the url, and leaking state between tests.

03.03.2025 15:05 — 👍 0    🔁 0    💬 1    📌 0

> Observables and setTimeout() need zone to detect those changes

Changes to template state only need a notification to Angular. This is built into signals automatically as well as async pipe. Or you can use markForCheck. Without the notification, you need zone but otherwise don’t.

02.02.2025 15:38 — 👍 1    🔁 0    💬 0    📌 0

I should also mention that you don’t need to use signals at all to go Zoneless. Signals just make it easier. Generally the only two requirements are using OnPush and not using NgZone.onStable/onMicrotaskEmpty.

31.01.2025 15:08 — 👍 2    🔁 0    💬 1    📌 0