mf-shared-deps

Analyze Module Federation configurations for shared and external dependency conflicts.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/brGuirra/funkonation --skill mf-shared-deps-brguirra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mf-shared-deps
Source: https://github.com/brGuirra/funkonation/tree/main/.agents/skills/mf-shared-deps
Command: npx skills add https://github.com/brGuirra/funkonation --skill mf-shared-deps-brguirra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps identify and resolve issues related to Module Federation shared dependencies, such as conflicts between shared and external configurations, problems with UI library sharing due to import transformations, and the detection of multiple versions of the same package in build artifacts.

Core Features & Use Cases

  • Conflict Detection: Identifies when a library is incorrectly configured in both shared and externals.
  • Transform Import Blocking: Detects when UI libraries like Ant Design or Arco are shared but transformImport is active, preventing sharing.
  • Version Mismatches: Flags instances where multiple versions of a shared package exist in build outputs, indicating failed version negotiation.
  • Use Case: Use this Skill when your host and remote applications are loading duplicate instances of a library, or when shared dependencies are failing to be shared correctly.

Quick Start

Run the mf-shared-deps skill with the project root as an argument.

Frequently Asked Questions about mf-shared-deps

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

FAQPage Schema
Why are my Module Federation shared dependencies loading duplicate instances in host and remote applications?

When UI libraries like Ant Design or Arco are shared in Module Federation, active transformImport settings prevent sharing by altering import paths. Detecting this configuration conflict ensures UI libraries are shared correctly across host and remote applications.

How do I check my webpack build for multiple versions of a shared package?

Configuring a library in both shared and externals causes Module Federation dependency conflicts. Identifying when a library is incorrectly placed in both configurations helps resolve sharing failures and ensures correct dependency management in webpack builds.

How do I debug Module Federation shared dependency issues in my frontend project?

Debug Module Federation shared dependency issues by analyzing configuration files to detect shared and external conflicts, transformImport blocking, and multiple package versions in build artifacts. Running a diagnostic skill with your project root as the argument reports these specific conflicts.

Can I use this to detect conflicts between shared and external dependencies in webpack?

Yes, you can detect conflicts between shared and external dependencies in webpack by analyzing your Module Federation configuration. This identifies when a library is incorrectly configured in both sections, causing shared dependencies to fail to load correctly.