William Lahti

> What about nasty little transpiling trick so that every "await foo()" is transpiled to "await foo(); app.tick()"? That way async await would be ~native, but with additional code on...

Warning aside, yes that does sound like this limitation. I use zone.js entirely separately from angular and am beginning to grow concerned we aren't going to solve this before I...

That's great news, but I do hope the team will keep exploring ways to enable this outside of angular. I use zonejs outside of angular for many purposes

Yeah maybe, personally I'm thinking the best bang for our buck is petitioning the Typescript developers to allow for downleveled async/await on higher ES targets. Might be an uphill battle...

You are always free to use a different change detection strategy other than Zone.js. Personally for Angular I use (and prefer) Zone.js by default and use Zone escape (via `NgZone#runOutsideAngular()`)...

> The Zone.js API is overwrought and over complicated. I agree, that's why I started modelling an alternative API which solves the same problem-space in a simpler way. Check out...

Ah of course- that does explain the difficulty-- wrapping the task handler to detect exceptions would be needed for Razmin and probably OpenTelemetry (assuming it has exception tracing), but for...

Wait, isn't this a bit of a problem? > Another subtlety with promises is that before and after callbacks are run only on chained promises. That means promises not created...

@avatsaev: Why so negative? Zone.js support for async/await in ES2017+ within Angular itself is effectively solved as of the commit referenced above. You're free to use it or opt for...

I'm going to approach your post as an Angular (frontend) developer. As I've noted above, Zone.js is far more useful outside of Angular than in, but it's clear you are...