In v21 apps are Zoneless by default. Meaning you need provideZoneChangeDetection if you want a zonejs based app.

Just finished today's stream! Wow we covered a lot - Learned what Zone.js is and why it is an actually impressive technology - Realized why we eventually got rid of it - Explored detectChanges vs markForCheck - we actually got to the bottom of this 😁 - Fispelled some myths like "Zonejs does change detection" and others - Figured out what can go wrong when you migrate a Zone.js-based app to Zoneless - Discovered how Angular MCP Server can help with a tool specifically tailored to help with Zoneless! Check if you missed it live ⬇️

I encountered a coding situation that neither Gemini 3.0, Claude Opus 4.5, nor Claude Sonnet 4.5 knew the issue. I was updating Angular v20 to v21 and after data was received from the Database it was not updating the User Interface. They all tried to add "setTimeout" in places. The issue was that v21 doesn't use ZoneJS by default like v20 was doing.

🅰️🎙️ ¡Hay una nueva edición del #Podcast de #DevTalles! En este hablamos repasamos las novedades del #Angular #SummerUpdate 2025, donde vimos mejoras clave como el soporte estable para aplicaciones sin #ZoneJS y más. ¡Además tiene video! Puedes verlo en:👇🏻youtu.be/OGZ2UnbO8nY?si=UYjR…

But I would strongly advise, if you are just starting with angular, and if you don't have to maintain legacy apps with zonejs. Just learn the new way with signals and go fully zoneless.

Zonejs is the "legacy" library behind angular that keeps all your nested components in angular aware of changes in your app so that components need to be recomputed to keep the UI state up to date. Usually referred to as change detection.

Very cool. Thank you zonejs for your service.

Very important to remember this. Also a great interview question 😁 Do you know why we have ZoneJS and what it does for #Angular?

ZoneJS !== Change Detection So mamy devs get this wrong. ZoneJS triggers CD That’s why we don’t need Zone in a long run.

Советую попробовать свежий Angular со standalone компонентами, на сигналах без zonejs ngrx стор

Debouncing will not preventing from firing CD. Zonejs is responsible from scheduling a CD on every event here. Solution is to listen outside the zone.

Paylogic, the gateway to buy Tomorrowland Belgium tickets uses Angular v18 with ZoneJS. Major win! (I mean, they could be NG19 zoneless thoujgh) cc: @Enea_Jahollari

I'm already using Primeng v19 with Tailwind and Nx, angular ssr v19.1 and everythings great. I didn't remove zonejs because the firebase library. but all my components are onPush more than 42 libs. btw, thanks to Angular ddd @ManfredSteyer

📣Deal of the Day📣 Jan 13 SAVE 45% TODAY ONLY! Modern Angular & selected titles: mng.bz/WrEx @Armandotrue Now in print! Discover the new features & techniques of the most modern versions of #Angular. #RxJS #NgRx #standalonecomponents #Zonejs #signals #Observables

En direct de #NantesJs, meetup #79 avec Anthony Pena pour la 2ème conférence. Adieu RxJs ! Vive les Signal ! Oh wait 😱 On parle de réactivité, #zoneJS, #RxJS, de design pattern observable,de signal. Merci Anthony pour le talk Merci @SNCFConnect pour l'accueil #Angular

This is basically what @analogjs (@angular v18) does with full signals (zonejs enabled still). SSR enabled Nitro backed by @bunjavascript preset. The website is behind Cloudflare but caching is not yet configured, I've just put it online. @brandontroberts what ya think? 🤭

Get rid of that zonejs 😅

Going zoneless in #Angular can have drastical impacts on your apps performance. When listening to zonejs-patched events which fire very frequent change detection gets crazy. See the example below where we are listening to scroll events. on every pixel move change detection will fire (see counter increasing) 𝘄𝗵𝗶𝗰𝗵 𝘁𝗿𝗶𝗴𝗴𝗲𝗿𝘀 𝗰𝗵𝗮𝗻𝗴𝗲 𝗱𝗲𝘁𝗲𝗰𝘁𝗶𝗼𝗻 𝗼𝗻 𝘆𝗼𝘂𝗿 𝘄𝗵𝗼𝗹𝗲 𝗰𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁 𝘁𝗿𝗲𝗲 𝗶𝗻 𝘁𝗵𝗲 𝘄𝗼𝗿𝘀𝘁 𝗰𝗮𝘀𝗲. In the second half of the clip I did not change any of the code (no need for runOutsideAngular) except using 𝗽𝗿𝗼𝘃𝗶𝗱𝗲𝗘𝘅𝗽𝗲𝗿𝗶𝗺𝗲𝗻𝘁𝗮𝗹𝗭𝗼𝗻𝗲𝗹𝗲𝘀𝘀𝗖𝗵𝗮𝗻𝗴𝗲𝗗𝗲𝘁𝗲𝗰𝘁𝗶𝗼𝗻 to make the application zoneless. @angular

anticipated changes (via zonejs) unless you’re running your subtree of components in detach mode or zoneless the entire application

When using async/await in #angular You are not really using async/await. [ What monkey can't patch? ] What Angular CLI does under the hood is transforming async/await to generators. ZoneJS can't MONKEY ;) patch async/await since there is no method there that can be patched. [ So can you use it? ] So, is it safe to use it? As long as the correct transformation is taking place you can use it. If you are using Angular CLI, it's taking place. But keep in mind you are not using native top level async/await. [ When native async/await :( ? ] The only way to use top level async/await is with zoneless app. Recently there was a PR merge that actually enabled that in zoneless :) - check it out in comments.