Tomas Rimkus

@joshuamorony you can find a more advanced version which fulfills your requirements on [medium](https://medium.com/gitconnected/trackid-infixing-trackby-capabilities-to-ngfor-in-a-centralised-way-across-your-angular-f1286f703469).

@JeanMeche I am not a bundler/minifier expert, but in my case input name is provided in the decorator (`@Input('ngForTrackByKey')`) and whether you name the property `key`, `k` or `foo` makes...

[ngxtension callPipe / ApplyPipe](https://ngxtension.netlify.app/utilities/pipes/call-apply/) can be used as a workaround. Also, [@memoize()](https://vlio20.github.io/utils-decorators/#memoize) decorator from `utils-decorators` or `Taiga UI` [@tuiPure](https://taiga-ui.dev/utils/pure) decorator can be used to memoize the function.

@montella1507 in the case you have described you are supposed to do the following ([documentation page](https://angular.io/guide/standalone-components#standalone-components-for-library-authors)): ```ts export const MODAL_COMPONENTS = [ ModalComponent, ModalBodyComponent, ModalHeaderComponent ] as const; ``` Then...

It's in v16: https://angular.io/guide/update-to-version-16#deprecations-highlights-in-angular-v16

@pkozlowski-opensource are you planning to finish this PR anytime in near future?

Based on the following rejections and @pkozlowski-opensource lack of response, it seems the PR will be just forgotten until it's closed due to its age. 

@AndrewKushnir This should not be closed until PR #48106 is merged. At this point even when using Angular v15.1, readonly array of standalone components can not be imported.

@cvandradg No, the issue reported here is that a **readonly** array of standalone components can not be imported in `NgModule`. The Angular team recommended "best practice" described in [the docs](https://angular.io/guide/standalone-components#standalone-components-for-library-authors)...

https://github.com/angular/angular/issues/52615#issuecomment-1802670101 @pkozlowski-opensource