Out-of-band type-checking for TypeScript and Template compilation

*Note 1: the original title of this issue was "Remove type-checking from the critical path of Angular builds (TypeScript and Template compilation)", but through community discussion we found "Out-of-band type-checking for TypeScript and Template compilation" more fitting).* *Note 2: This proposal has its origin in [RFC: Exploration of use-cases for Angular JIT compilation mode](https://github.com/angular/angular/issues/43133) and aims to address the concerns around AOT builds being too slow compared to the JIT alternative.* *Note 3: 📺 Check out the [video recording of a community discussion about this proposal](https://youtu.be/FbJLC7GxAAs?t=3714) @ [angularnation.net](https://www.angularnation.net/)* ## The problem Currently, precious hundreds of milliseconds, but often more commonly many seconds, are being spent on type-checking code of Angular applications as developers edit the code using interactive workflows (like `ng serve`, `ng test --watch`, etc). Not only does this increase the latency, and decrease the number of iterations per minute, it also makes it impossible to see results of a change in the browser if the change doesn't pass the type-checking step. This makes it hard to experiment, and explore, which impacts creativity, and forces developers to either iterate less, or take the time to make the compiler happy, just to find out that they are heading down the wrong direction. But it doesn't have to be this way... we can have both a faster iteration cycle, a

Posted by IgorMinar on Aug 12, 2021, 7:22 PM

Tags

• reliability (Network)

Related issues

• I can't recall who said it, but "The biggest problem with golden ages is that you never realize you're in one until it's over".
• [BUG] No response from API error when Advisor is triggered
• I thought the general premise is that humans can't form social groups bigger than around ~200.
• great, now can we convince the rest of the internet to start adding AAAA records and ipv6 endpoints for things.
• > It's only with the emergence of whiny, persnickety Unix devs who refused to leave the comforting embrace of their editor of choice that...
• Contrary to some other comments: no, IPV6 hasn't taken over the world at all.