Joost Koehoorn

The increase in memory is totally expected and has nothing to do with ICs/JIT/V8; hidden classes are obtained using a class transition graph so they are nicely shared if an...

@victorsc I looked into a profiler trace for your reproduction and one thing stood out: TypeScript type checking was taking ~35s of a total of ~50s. The reason is that...

I briefly talked to @alan-agius4 and he rightfully mentioned that `skipLibCheck` will also disabled type-checking of local .d.ts files, which is not something we want to do by default. That...

The change to enable `skipLibCheck` by default has been retracted from #1764. It's not universally safe as it also causes local declaration files not to be checked. For projects with...

What's the problem here, exactly? `@angular/material` does have a primary entry-point, it's just empty. Would that not be a possibility with ng-packagr for some reason?

@klemenoslaj ah, I see. I can't think of any changes in this area, so I expect that to still behave the same. As you said, exporting a dummy could be...

This error is expected; the value of the `STANDALONE_COMPS` array is only visible within the same compilation unit, not to downstream compilations that consume the lib through its .d.ts declaration...

I can't look into it further now as I'm on vacation without a laptop, so can't test with the repro from mobile for now.

I am going to reopen this issue as umbrella issue for multiple copies of `@angular/core`, as I have always been referring to this issue for its duplicates.

It would require a different approach to how pipes are declared in the type-checker, specifically using a type constructor. A lot more details are in https://github.com/angular/angular/pull/40870#issuecomment-780882880. There's also [this comment](https://github.com/angular/angular/issues/41861#issuecomment-832774005).