How does Angular's newer zoneless change detection improve on the traditional Zone.js based approach?

Traditional Angular relies on Zone.js to automatically detect when something might have changed, such as after any asynchronous operation, then checks the entire app just in case. Zoneless change detection instead relies on explicit signals to know exactly what changed and where, letting Angular update only the specific parts of the page that actually need it, without the overhead of Zone.js patching every asynchronous browser API.

// A zoneless Angular app relies on signals to know exactly what changed
bootstrapApplication(AppComponent, {
  providers: [provideExperimentalZonelessChangeDetection()]
});