Skip to content

bug(various): ReferenceError Cannot access 'X' before initialization #19461

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mcalmus opened this issue May 27, 2020 · 2 comments
Closed

bug(various): ReferenceError Cannot access 'X' before initialization #19461

mcalmus opened this issue May 27, 2020 · 2 comments

Comments

@mcalmus
Copy link
Contributor

mcalmus commented May 27, 2020

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

  • 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
@mcalmus mcalmus added the needs triage This issue needs to be triaged by the team label May 27, 2020
@crisbeto
Copy link
Member

Duplicate of #19454.

@crisbeto crisbeto removed the needs triage This issue needs to be triaged by the team label May 27, 2020
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants