Alex Rickabaugh

This PR was merged into the repository by commit 08b664d3c81712992032ab32757fdcad9eb8554a.

@dali-trabelsi the reproduction provided, with a precompiled (and minified!) custom element is not a minimal reproduction. We should be able to see what's going on in the custom element.

This PR was merged into the repository by commit 02d5e8d79dc1f5dd70f9d997d6ecb1632d93b86e.

As @JoostK's analysis shows, this is an interaction between `strictTemplates: false` and `noImplicitAny`. I don't think we're going to make any changes to the non-`strictTemplates` mode at this point -...

This seems like a good candidate for an extended diagnostic instead - `[ngClass]` with a literal could be converted to individual class bindings.

#46146 will be in 14.1 which adds this warning for `ngIf` & friends.

I believe that this is working as intended in Angular today. Basically, to use the JIT compiler, you have to: 1. import `@angular/compiler` to load the JIT compiler 2. configure...

I think the comparison between `Observable` and `AsyncIterator` is misleading here. `NgFor` requires a synchronous array for rendering, even if that array is produced asynchronously. That is, in the invocation`*ngFor="let...

As @JoostK says, the issue here is really that binding to a DOM event is completely legal in Angular, even when the element is otherwise a component. However, there's definitely...

I would love to see some sort of lazy-loading of interceptors. Thanks for the design proposals! I'm tagging this as a use-case request to allow for discussion. I feel like...