Alexander von Weiss

we had a similar issue, see https://github.com/angular/angular/issues/44859#issuecomment-1024093837 - when `array[1234] ?? 'fallback'` threw a warning about supposedly `array[1234]` never being `null`

So there mere presence of a method `ngOnDestroy` lets angular call it upon component destruction. How about the mere presence of a: ```typescript class MyComponent { public ngDestroy = new...

Instead of increasing the surface and complexity of the framework because we humans are to lazy to write down the already available pattern, this could instead be solved with better...

One can now download chrome version 88 from the dev channel https://www.google.com/chrome/dev/?extra=devchannel. If you use lighthouse inside there, you'll see the LCP calculated with the new method. And google announced...

~The current LCP metric (as of 89.0.4356.6) seems not to handle picture elements like:~ ```typescript ``` ~So we now give chrome the jpeg treatment - twice as big files with...

@rockeynebhwani thx for asking so I went into the numbers and looked more thoughtfully. Seems like my claim was wrong. I misinterpreted LCP being above TTI as LCP not working...

> The Angular+Universal+PWA was simply too heavy IMHO it's not angular, it's lighthouse. Simulated moto 4g - an over 7 year old device - is just weirdly outdated. >= 4...

If I lighthouse e.g. https://www.vashi.com/loose-diamonds/marquise, then chrome identifies the first image in the product list for LCP  But if I open the same site with javascript disabled, thus only...

Could you also test with wrapping the section with `console.time('bootstrap')` & `console.timeEnd('bootstrap')` with dev tools closed, and then inspect the console output afterwards? Having a debugger attached can slow down...

Angular doesn't support lazy loading/resolving templates at runtime in node.js. Thats why https://yarnpkg.com/package/jest-preset-angular replaces `templateUrl: './foo.html` with `template: ''` at transform time.