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
Reproduction of the bug/regression with instructions
I am using this lib in an NX monorepo. I am implementing a header-nav in a publishable lib which contains a mat-menu. When I try to use this header-nav and click the mat-menu trigger, I get the following error:
I have already opened a ticket at the official Angular components repo and @devversion could confirm that with your builder two CDK version are existing: angular/components#30686 (comment)
I don't have a lot of context about Module Federation here, but out of curiosity I've looked more. I believe the issue could be?! that the shared chunks that are now part of e.g. @angular/cdk/fesm2022 aren't picked up as "shared" because (thesis) this plugin/federation only picks up the chunk specified in the exports[entrypoint].default export condition?
With what library do you have an issue?
native-federation
Reproduction of the bug/regression with instructions
I am using this lib in an NX monorepo. I am implementing a header-nav in a publishable lib which contains a
mat-menu
. When I try to use this header-nav and click themat-menu
trigger, I get the following error:I have already opened a ticket at the official Angular components repo and @devversion could confirm that with your builder two CDK version are existing: angular/components#30686 (comment)
I have already built a reproduction of the error in a public repo: https://github.com/JuNe98/nx-menu-bug
I also can confirm that the error only come up in Angular Material Version 19.2.4 or newer. 19.2.3 works fine.
Expected behavior
I would expect open the
mat-menu
causing no error.Versions of Native/Module Federation, Angular, Node, Browser, and operating system
Native Federation: 19.0.16
Angular: 19.2.3
Angular Material: >=19.2.4
Other information
No response
I would be willing to submit a PR to fix this issue
The text was updated successfully, but these errors were encountered: