Suggest an editImprove this articleRefine the answer for “Can Zone.js be fully disabled when using signals?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**Yes, it can.** Signals track changes and update the template on their own without Zone.js: in `main.ts`, at application startup, you set `zone: 'noop'`, and everything based on `signal`, `computed`, and `effect` keeps working reactively. **Key point:** signals allow you to fully disable Zone.js, and the application still stays reactive and updates itself.Shown above the full answer for quick recall.Answer (EN)ImageYes, it can. Signals track changes and update the template **without Zone.js**. Angular can now work fully reactively, without a "zone" that used to intercept all events and trigger updates manually. ### How it is done: In `main.ts`, at application startup, you specify: ```ts import { bootstrapApplication } from '@angular/platform-browser'; import { AppComponent } from './app/app.component'; bootstrapApplication(AppComponent, { zone: 'noop', // disables Zone.js }); ``` ### What happens next: - everything based on `signal`, `computed`, and `effect` keeps working; - Angular will update only the parts of the template that depend on signals; - no "zones" are needed anymore. **Summary:** yes, signals let you fully disable Zone.js, and the application still stays reactive and updates itself.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.