Question 1

What is zoneless Angular?

Accepted Answer

Running Angular without Zone.js patching, relying on signals and explicit notifications for updates. provideExperimentalZonelessChangeDetection (or current zoneless APIs) removes Zone overhead. Async work must update signals/mark views dirty.

Question 2

Why move to zoneless?

Accepted Answer

Less monkey-patching, clearer reactivity, better performance predictability, smaller bundle. Requires discipline: third-party libs that expect Zone may break. Signals become the primary update path.

Question 3

How do you trigger UI updates without Zone.js after setTimeout?

Accepted Answer

Update a signal or call ChangeDetectorRef.markForCheck/detectChanges inside the callback. Wrapping in NgZone.run is the Zone-era approach; zoneless prefers signals. Test carefully.

Question 4

What library risks appear when going zoneless?

Accepted Answer

Libs that rely on Zone to refresh UI after async work may not update until you bridge updates. Prefer signal-friendly patterns. Audit charting/auth SDKs. Add thin adapters that set signals on callbacks.

Zoneless Angular Angular Interview Questions

Other Angular interview topics