Webpack 5 / Module Federation

Description

Webpack 5 has a new feature called Module Federation (I’m sure it’s caught some folks’ attention by now), allowing you to at runtime import parts of bundles from other applications. I could see this slotting into nx quite neatly, for example by allowing the exposes property of the plugin to be set in nx.json:

{
  "projects": {
    "chrome": {
      "exposes": {
        "AppContainer": "src/App.tsx"
      },
      "tags": []
    },
    "chrome-e2e": {
      "tags": [],
      "implicitDependencies": ["chrome"]
    },
    "settings": {
      "tags": [],
      "exposes": {
        "Settings": "src/Settings.tsx"
      }
    }
  }
}

I tried looking for an existing issue but couldn’t find any, so thought it would be worth bringing up. Would love to hear what you think about Module Federation in general, and what it could mean for NX. Thanks ❤️

Some links:

• Documentation
• Demo

[crates]

@firxworx / @vitorcamachoo / @agoncharuks / @georgewilde / @elenasch / @vanuj:

Webpack 5 is on the Nx roadmap, slated for release with version 13 in October of this year.

[smasala]

Agree with @Vynlar. This would be a huge game changer in terms of creating isolated buildable and deployable apps which can then be part of a single and larger SPA.