-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Webpack Module Federation Docs #4283
Comments
For maintainers only:
|
After digging into Module Federation codebase, I realized that https://webpack.js.org/concepts/module-federation/ is presenting outdated information. With this PR webpack/webpack#10960, |
Facing the same issue. As of now we are using examples to understand the API, a proper documentation of API is very important. |
Yes same here, there is very little documentation for |
for me, I got lost trying to figure out how to use the OverridablesPlugin (https://webpack.js.org/concepts/module-federation/#building-blocks) edit: sorry, this is the same issue reported 3 comments up. |
I think this is also supposed to be covered under #3757 |
Feature request
My company is evaluating micro-frontend frameworks for a platform. Webpack is high up on the list of potential frameworks, but unfortunately, the webpack module federation docs are not up to the standard of the more stable webpack docs.
What is the expected behavior?
What is motivation or use case for adding/changing the behavior?
Making Webpack module federation adoptable
How should this be implemented in your opinion?
Similar to the other webpack API docs
Are you willing to work on this yourself?
no, I don't have the required knowledge or the time unfortunately. If someone with the knowledge would provide me with details, I can submit a PR.
The text was updated successfully, but these errors were encountered: