Deep Dive into the Angular Compiler | Alex Rickabaugh | #AngularConnect

For most of us, the Angular compiler is just a part of the build - it's that thing that happens before the "real" work of compilation: 92% chunk asset optimization. But how does it actually work? What does the Angular compiler _do_ when it's taking our Angular code and generating Javascript?

About Alex Rickabaugh
Alex Rickabaugh is a software engineer at Google, and for the last three years has been a core member of the Angular team. Throughout his time on Angular, Alex has worked on the Service Worker implementation for Progressive Web Apps, server-side rendering support, and a rewrite of the HTTP API. Currently, he works on the Angular Compiler, getting it ready for the next generation architecture, Angular Ivy.

[chriswininger]

I love that trick where they add offsets into the template to the generated typescript to link back to the template on error. Such a beautiful hack.

[blackblather]

Yo that part about adding the number comments is so ugly and cool at the same time. I love and hate it 🤣🤣

[kresimirnurnberger]

Great talk and great work! Enjoyed every minute of it.

[mohammedelhadididi]

When alex said that compilation process pass through 5 steps (3 like a normal typescript compiler and 2 angular specials), is that true only when using AOT compilation or it doesn't matter if it's JIT or AOT compilation ?

[coachkerni]

First of all: great talk :)
However I am not getting one thing:
When the typescript compiler is written in typescript, who is compiling the compiler? 🤷‍♂️

[masterlup]

25:45 I dont understand what Alex means by "template in external file" and why is that a problem with the view engine :/.

[masterlup]

19:23 `imports: [...CONFIG.modules]`, we have to spread, right?