Importing standalone components from lib into other lib's module breaks build

Type of Issue

[x] Bug Report
[ ] Feature Request

Description

The build breaks as sone as angular standalone components are added to another lib’s ngModule via spreaded array.

   libs/other-lib/src/lib/other-lib.module.ts:7:12 - error NG1010: Value at position 1 in the NgModule.imports of OtherLibModule is not a reference
     Value could not be determined statically.

   7   imports: [CommonModule, ...STANDALONE_COMPS],
                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

     libs/other-lib/src/lib/other-lib.module.ts:7:27
       7   imports: [CommonModule, ...STANDALONE_COMPS],
                                   ~~~~~~~~~~~~~~~~~~~
       Unable to evaluate an invalid expression.

Corresponding issue inside the nrwl nx repo: https://github.com/nrwl/nx/issues/11451 Workaround: https://github.com/nrwl/nx/issues/11451#issuecomment-1211725201

How To Reproduce

The following is a nrwl nx repo which used buildable libraries. This process uses ng-packagr under the hood.

https://github.com/TomTomB/nx-ng-standalone-comps-issue

• Clone the repo
• Run npm install
• Run npm run ng build

Expected Behaviour

This should work in the same way as e.g. spreading a (non standalone) components array into the ngModule’s delarations.

Version Information

$ node_modules/.bin/ng-packagr --version
ng-packagr: ~14.1.0
@angular/*: ~14.1.0
typescript: 4.7.4
rxjs: ~7.5.6
node: 16.x
npm/yarn: yarn@3.2.1 (PnP disabled)
nx: 14.5.4

[JoostK]

This turned out to be missing support from the AOT compiler which has been addressed in angular/angular#48091.

^{I cannot close issues in this repo. EDIT I can now!}

[montella1507]

Hi @JoostK any news regarding this issue, please?