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
Module Federation with Library Type Module (ESM) is not working #14111
Comments
@sokra any idea on this |
@ckken Try setting library.type to
|
Fixed #14827 |
no work also in 5.64.4 when build bundle |
Please create reproducible test repo |
Are there any simple demos? My cases are more complex |
Maybe I set it wrong |
That is why I asked repo, you do not need to provide the entire project, cut it to reproduce repo |
https://github.com/saravanan10393/mf-es-module it work! thanks |
It works with ESM? So I don't need to check it? |
Is there a place or documentation where I can see all the library types? I'm passing through the same problem above, with same configuration, but I can't find a place where there's a detailed explanation of library types. |
You can open an issue in our docs and we will try to improve |
i still expirience this issue: issue including reproduction, |
Bug report
What is the current behavior?
When setting
in module federation plugin config, the generate remote entry is not exporting anything. Or simply saying, consuming remote is not working.
If the current behavior is a bug, please provide the steps to reproduce.
(https://github.com/saravanan10393/mf-es-module)[Here is the reproduce repo] also (https://gist.github.com/saravanan10393/8185ef0a3e56f9419bbc5a299815aad4)[here is the generated removeEntry of app1.]
What is the expected behavior?
The remoteEntry with ESM target support is needed.
Other relevant information:
webpack version: 5.51.1
Node.js version: 14
Operating System: Mac
Additional tools:
The text was updated successfully, but these errors were encountered: