You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steps to reproduce:
I have not yet been able to reproduce this using a trivial case in Stackblitz.
After updating to version 10.0.0-next.2 (from 10.0.0-next.1) I am seeing instances similar to:
ReferenceError: Cannot access 'MatSelectionList' before initialization
at list.js:589
at Module../node_modules/@angular/material/ivy_ngcc/fesm2015/list.js (list.js:649)
I have seen this in one module as above and another where 'MatCalendar' is the component. The broken page then fails to load regardless of whether it was accessed directly through a URL or via a router link from another module.
Expected Behavior
Page should load without error.
What behavior were you expecting to see?
Actual Behavior
What behavior did you actually see?
Page fails to load with ReferenceError
Environment
Angular: 10.0.0-rc.0
CDK/Material: 10.0.0-next.2
Browser(s): Chrome, FF, Safari
Operating System (e.g. Windows, macOS, Ubuntu): macOS
The text was updated successfully, but these errors were encountered:
Reproduction
Steps to reproduce:
I have not yet been able to reproduce this using a trivial case in Stackblitz.
After updating to version 10.0.0-next.2 (from 10.0.0-next.1) I am seeing instances similar to:
ReferenceError: Cannot access 'MatSelectionList' before initialization
at list.js:589
at Module../node_modules/@angular/material/ivy_ngcc/fesm2015/list.js (list.js:649)
I have seen this in one module as above and another where 'MatCalendar' is the component. The broken page then fails to load regardless of whether it was accessed directly through a URL or via a router link from another module.
Expected Behavior
Page should load without error.
What behavior were you expecting to see?
Actual Behavior
What behavior did you actually see?
Page fails to load with ReferenceError
Environment
The text was updated successfully, but these errors were encountered: