• module-federation-types-plugin
  • Installation
  • CLI Tool
    • CLI options
  • Plugin Configuration
    • Exposed modules
    • federation.config.json
    • webpack.config.js
    • Plugin Options
  • Consuming remote types
  • Templated Remote URLs
    • Importing from self as from remote
    • CI/CD
  • History
  • Feature comparison tables

This package exposes a Webpack plugin and a node CLI command make-federated-types.

It compiles types into a dist/@types/index.d.ts file and downloads compiled remote types from other federated microapps into src/@types/remotes folder.

Global type definitions from src/@types/*.d.ts are included in compilation.

All paths can be customized to meet your environment.

npm i @cloudbeds/webpack-module-federation-types-plugin

The standalone make-federated-types script compiles types to the dist/@types folder, the same way as the plugin does. It is useful for testing and debugging purposes or when it is not desired to update types automatically during the build process.

This script should not be used in CI as the build script, that executes the plugin, already writes the types.

The main requirement for the tool is the existance of federation.config.json file.

It can be called like so:

npx make-federated-types

Or it can be added to package.json:

{
  "scripts": {
    "make-types": "make-federated-types"
  }
}

Create a federation.config.json that will contain the remote name and exported members. This file is mandatory for the standlone script but not required for the plugin.

Properties of this object can be used in Webpack's ModuleFederationPlugin configuration object and required by the standalone script. Example:

Requirements:

• all paths must be relative to the project root
• the /index file name suffix is mandatory (without file extension)

{
  "name": "microapp-42",
  "exposes": {
    "./Button": "./src/view-layer/components/Button",
    "./Portal": "./src/view-layer/index"
    "./Http": "./src/wmf-expose/Http"
  }
}

Spread these properties into your ModuleFederationPlugin configuration and add ModuleFederationTypesPlugin to every microapp, like so:

import webpack from 'webpack';
import { ModuleFederationTypesPlugin } from '@cloudbeds/webpack-module-federation-types-plugin';

import federationConfig from '../federation.config.json';

const { ModuleFederationPlugin } = webpack.container;

module.exports = {
  /* ... */
  plugins: [
    new ModuleFederationPlugin({
      ...federationConfig,
      filename: 'remoteEntry.js',
      shared: {
        ...require('./package.json').dependencies,
      },
    }),
    new ModuleFederationTypesPlugin({
      downloadTypesWhenIdleIntervalInSeconds: 120,
    }),
  ],
}

To enable verbose logging add folowing in webpack config:

  infrastructureLogging: {
    level: 'log'
  }

When you build your microapp, the plugin will download typings to src/@types/remotes folder

Templated URLs are URLs to the external remotes that are substituted in runtime using a syntax that is used in module-federation/external-remotes-plugin

Example: for a mfeApp remote entry:

{ mfeApp: 'mfeApp@[mfeAppUrl]/remoteEntry.js' }

The [mfeAppUrl] placeholder refers to window.mfeAppUrl in runtime. That part is replaced by URL that is fetched from a remote manifest file:

new ModuleFederationTypesPlugin({
  remoteManifestUrls: {
    mfeApp: 'https://localhost:4480/remotes/dev/mfe-app-remote-entry.json',
    registry: 'https://localhost:4480/remotes/dev/remote-entries.json',
  }
})

or

new ModuleFederationTypesPlugin({
  cloudbedsRemoteManifestsBaseUrl: 'https://localhost:4480/remotes/dev',
})

See RemoteManifest and RemotesRegistryManifest in types.ts to observe the signature.

Eventually the origin, e.g. https://localhost:9082 is used to fetch the types from

With the registry field multiple remote entry URLs can be substituted from a single JSON file. Depending on your architecture, this could be the only URL that you need to specify. Example of a remote-entries.json file for a Prod environment:

[
  {
    "scope": "mfeApp1",
    "url": "https://mydomain.com/mfd-app-1/remoteEntry.js"
  },
  {
    "scope": "mfeApp2",
    "url": "https://mydomain.com/mfd-app-2/remoteEntry.js"
  },
  {
    "scope": "mfeApp3",
    "url": "https://mydomain.com/mfd-app-3/remoteEntry.js"
  }
]

You can have registries with URLs that target bundles that was built for specific deployment environment.

It is also possible to add self as a remote entry to allow importing from self like from a remote. Example for an mfeApp microapp:

remotes: {
  mfeApp: 'mfeApp@[mfeAppUrl]/remoteEntry.js'
}

It is suggested to download types in a CI workflow only when a dev branch is merged to the main branch, that is the time when the deployment to dev/stage/prod is about to happen. In this case the downloaded types will correspond to the latest versions of dependent microapps, resulting in valid static type checking against other microapps code in their main branch.

When DEPLOYMENT_ENV env variable is set to devbox, remote types are not downloaded. That is to allow a microapp to download types from dev branch of another microapp. Otherwise, the build would fail on static type checking phase. A dev branch of a microapp may depend on another dev branch of another microapp, thus will have to commit those types to avoid failing workflows.

Having Webpack 5 module federation architecture in place it's tedious to manually create/maintain ambient type definitions for your packages so TypeScript can resolve the dynamic imports to their proper types.

While using @ts-ignore on your imports works, it is a bummer to lose intellisense and type-checking capabilities.

Inspired by several existing solutions:

• @touk/federated-types a fork of pixability/federated-types
• ruanyl/dts-loader
• ruanyl/webpack-remote-types-plugin, a wmf remotes-aware downloader of typings that can be used also with files emitted using @touk/federated-types . Example.
• @module-federation/typescript from the creator of Webpack Module Federation, Zack Jackson (aka ScriptAlchemy)

Zack Jackson was asked for help with several issues around his plugin. There was a hope that he can suggest some solutions to the exposed problems, to no avail. After a month of waiting this package was built.

*Runtime microapp imports refers to templated remote URLs that are resolved in runtime using module-federation/external-remotes-plugin

*Synchronization refers to webpack compile hooks

*Excessive recompilation refers to the fact that the plugin is not smart enough to detect when the typings file is changed. Every time a d.ts file is downloaded, webpack recompiles the whole bundle because the watcher compares the timestamp only, which is updated on every download.