mf-config-check
Check Module Federation build configuration: verify correct MF plugin for the bundler, async entry configuration, exposes key format, and exposes path existence. Use when modules cannot be correctly exposed, expected modules are missing from the build output, or runtime initialization errors occur.
How do I install this agent skill?
npx skills add https://github.com/module-federation/core --skill mf-config-checkIs this agent skill safe to install?
- Gen Agent Trust Hubwarn
This skill analyzes Module Federation configurations. While functional, it contains vulnerabilities where a malicious project could exploit unsanitized data to execute unauthorized shell commands or probe the file system for the existence of sensitive files.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerpass
2 files scanned · No issues
What does this agent skill do?
Step 1: Call the mf-context Skill (pass $ARGUMENTS) to collect MFContext.
Step 2: Serialize MFContext to JSON and pass it to the check script via the --context argument:
node scripts/config-exposes-check.js --context '<MFContext-JSON>'
Process each item in the output results array:
CONFIG-PLUGIN · warning — incorrect or missing MF plugin
- Based on the detected bundler and installed packages, the recommended plugin is:
- Webpack only:
@module-federation/enhancedor@module-federation/enhanced/webpack - Rspack only:
@module-federation/enhanced/rspack(recommended) or@module-federation/rspack - Rsbuild:
@module-federation/rsbuild-plugin(recommended), or the Rspack plugin - Modern.js:
@module-federation/modern-js-v3for@modern-js/app-tools≥ 3.0.0, otherwise@module-federation/modern-js; falls back to Rspack/Webpack plugin based on the underlying bundler - Next.js:
@module-federation/nextjs-mf
- Webpack only:
- Show the detected bundler, installed MF-related packages, and the recommended plugin
CONFIG-ASYNC-ENTRY · warning — async entry not configured (maps to RUNTIME-006)
experiments.asyncStartup = trueis not set in the bundler config- This setting is required by most bundler setups to avoid runtime initialization errors
- Exception: not required when using
@module-federation/modern-js-v3or@module-federation/modern-js - Note: Rspack requires version > 1.7.4 to support this option
- Reference: https://module-federation.io/blog/hoisted-runtime.md
- To check: read
bundler.configFilefrom MFContext and look forexperiments.asyncStartup
CONFIG-EXPOSES-KEY · warning — key does not start with ./
- MF spec requires exposes keys to start with
./(e.g.,"./Button"not"Button") - Inform the user of the specific key name and guide them to correct the format
CONFIG-EXPOSES-PATH · warning — path does not exist
- The file referenced by the exposes value does not exist in the project. Show the specific key and incorrect path.
- The check must match the exact file extension (e.g.,
.tsx≠.ts) - Common causes:
- Typo in file path
- Wrong file extension
- Incorrect relative path base (should be relative to project root)
When results is empty
- Inform the user that plugin selection, async entry config, and exposes passed all checks
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/module-federation/core/mf-config-check">View mf-config-check on skillZs</a>