build: release output contains forward references that break at runtime

[lacolaco]

Reproduction

Use StackBlitz to reproduce your issue: https://stackblitz.com/fork/components-issue

Steps to reproduce:

1. https://stackblitz.com/edit/angular-wudjzd?
2. Downdoad app as zip
3. open zip, npm install and npm start

Expected Behavior

As well as on Stackblitz, it should work correctly on the local environment. But it isn't.

Actual Behavior

Datepicker throws a runtime error.

I think maybe it is caused by ngcc process but I'm not sure.

Environment

Angular CLI: 10.0.0-rc.0
Node: 12.14.1
OS: darwin x64

Angular: 10.0.0-rc.0
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
Ivy Workspace: <error>

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.1000.0-rc.0
@angular-devkit/build-angular     0.1000.0-rc.0
@angular-devkit/build-optimizer   0.1000.0-rc.0
@angular-devkit/build-webpack     0.1000.0-rc.0
@angular-devkit/core              10.0.0-rc.0
@angular-devkit/schematics        10.0.0-rc.0
@angular/cdk                      10.0.0-next.2
@angular/material                 10.0.0-next.2
@ngtools/webpack                  10.0.0-rc.0
@schematics/angular               10.0.0-rc.0
@schematics/update                0.1000.0-rc.0
rxjs                              6.5.5
typescript                        3.9.3
webpack                           4.43.0

[devversion]

Thanks for this issue. That is a known issue. It's related to: microsoft/TypeScript#27519 and angular/angular#30106.

[mcalmus]

Any workarounds for this? In which version did this begin? I've successfully messed up my working copy of code but am not sure which change(s) caused the problem.

[devversion]

@mcalmus It broke with angular/angular@a1001f2, and we started building release output with those changes in next.2. Staying on next.1 is the current workaround.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}