mf-config-check

Exposed modules are often missing because the exposes keys lack the required `./` prefix or the referenced file paths are incorrect. Validating your Module Federation configuration checks these path formats to ensure modules are bundled correctly.

Runtime initialization errors typically occur when `experiments.asyncStartup` is not configured correctly. Checking your Module Federation setup verifies this async entry configuration to prevent startup crashes.

Yes, the configuration validation supports multiple bundlers including Rspack, Webpack, Rsbuild, Modern.js, and Next.js. It verifies that the correct Module Federation plugin is installed for your specific build tool.

Module Federation exposes keys must follow the `./` prefix convention, such as `./Button`. Validating your configuration detects incorrect key formats and verifies that the referenced source paths actually exist on disk.

Debugging a Module Federation configuration requires analyzing your build setup with a Node.js script. This checks for the correct bundler plugin, async entry setup, and valid exposes paths to resolve build errors.