Skip to content

Webpack Module Federation Docs #4283

Open
@RyanCCollins

Description

@RyanCCollins

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?

  • The docs for module federation are missing API Docs containing explanation of the properties on the ModuleFederationPlugin and low-level container plugins.
    • It's not clear how shared modules, exposes and remotes work. The only way to figure it out is to dig into the examples.
    • Not clear what overrides vs. overridables are and how they relate to the plugin.
    • A deeper dive into shared modules, including their optional properties, would be helpful.
    • Other properties should be documented to show their intent and data type.

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions