angular: bug(upgrade): infinite digests with setTimeout (repro inside)

@petebacondarwin any update? Will this be fixed in the near future?

+1 Any update on this please?

We have some ideas that might help but key people are unavailable this week and next. I’ll update in a couple of weeks

We are generally not keen on changing $digest to $evalAsync for the digest that is run when the microtask queue is empty, because this tends to hide programming errors (which often have hard-to-track-down performance implications).

This unfortunately means that running setTimeout in a watcher will lead to infinite digest errors, unless you change it to run outside of the Angular zone. _{To be clear, you can still use setTimeout in the watch listener function:}

scope.$watch(
  () => {
    // Watch function.
    // Do NOT use `setTimeout()` here (unless you explicitly run it outside the Angular zone).
  },
  () => {
    // Watch listener function.
    // You can use `setTimeout()` here.
  }
)

The new downgradeModule(), which decouples the change detections of the two frameworks, could possibly help in such situations. (Docs will be added with #18487.)