mf-config-check

Validate Module Federation build configurations for plugin, async entry, and exposes paths.

Updated Mar 15, 2026

Search Tags:#debugging #configuration #webpack #build tools #module federation #rspack

Ready to run

npx skills add https://github.com/brGuirra/funkonation --skill mf-config-check-brguirra

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mf-config-check
Source: https://github.com/brGuirra/funkonation/tree/main/.agents/skills/mf-config-check
Command: npx skills add https://github.com/brGuirra/funkonation --skill mf-config-check-brguirra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps identify and resolve common configuration issues within Module Federation setups, preventing build errors and runtime problems.

Core Features & Use Cases

Bundler Plugin Verification: Checks if the correct Module Federation plugin is installed for your bundler (Webpack, Rspack, Rsbuild, Modern.js, Next.js).
Async Entry Configuration: Ensures experiments.asyncStartup is correctly set to prevent runtime initialization errors.
Exposes Key and Path Validation: Verifies that Module Federation exposes keys follow the ./ prefix convention and that the referenced paths actually exist.
Use Case: When modules are not being exposed correctly, are missing from build outputs, or when runtime initialization errors occur, this Skill provides specific diagnostics and recommended fixes.

Quick Start

Use the mf-config-check skill to analyze the module federation configuration for the current project.

Frequently Asked Questions about mf-config-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Why are my Module Federation exposed modules missing from the build output?▼

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.

How do I fix Module Federation runtime initialization errors during async startup?▼

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.

Does this Module Federation config check support Rspack and Next.js bundlers?▼

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.

What is the correct format for Module Federation exposes keys?▼

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.

How do I debug a Webpack Module Federation plugin configuration?▼

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.