mf-bridge-check

Validate Module Federation Bridge API usage in producer export-app configurations.

2.6k|423|Updated Oct 24, 2020
One-click install
npx skills add https://github.com/module-federation/core --skill mf-bridge-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mf-bridge-check
Source: https://github.com/module-federation/core/tree/main/skills/mf-bridge-check
Command: npx skills add https://github.com/module-federation/core --skill mf-bridge-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, and includes scripts (resource) components.

What problem does it solve?

This Skill helps ensure that Module Federation integrations are stable and correctly implemented by verifying that producers export the necessary export-app and consumers use recommended Bridge APIs.

Core Features & Use Cases

  • Producer Verification: Checks if a producer correctly exposes an export-app entry point.
  • Consumer Guidance: Recommends using official Bridge APIs like createRemoteAppComponent for consumers.
  • Use Case: When micro-frontend sub-app integration is unstable or errors occur, use this Skill to diagnose potential issues with how applications are exposing or consuming remote components.

Quick Start

Run the mf-bridge-check skill with the project root as an argument.

Frequently Asked Questions about mf-bridge-check

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

FAQPage Schema
Why does my Module Federation micro-frontend sub-app integration fail with instability errors?

Module Federation micro-frontend integration instability often stems from producers missing the `export-app` entry point or consumers not using recommended Bridge APIs like `createRemoteAppComponent`.

How do I validate my Module Federation Bridge API configuration?

To validate your Module Federation Bridge API configuration, run the bridge-check script with your project root and the required mf-context data to verify producer and consumer compliance.

What is the correct way to expose a producer export-app in Module Federation?

A correct producer `export-app` in Module Federation must expose the necessary entry point, which this validation process checks to ensure remote components are properly integrated and consumed.

Do I need Node.js to run a bridge-check for micro-frontend integration issues?

Yes, you need Node.js installed because the bridge-check script relies on it to execute the validation logic and analyze the collected mf-context data for integration errors.

How do I know if my consumer application is using the recommended Bridge APIs?

You can verify if your consumer application uses recommended Bridge APIs by running a validation check that analyzes your project context and recommends adopting official APIs like `createRemoteAppComponent`.