mf-module-info

Fetch metadata and manifest details from remote Module Federation modules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers understand the configuration and exposed modules of remote Module Federation applications, simplifying integration and debugging.

Core Features & Use Cases

  • Metadata Fetching: Retrieves publicPath, remoteEntry URL, and type declaration locations.
  • Manifest Parsing: Extracts exposes, remotes, and shared dependencies from mf-manifest.json.
  • Two Modes: Works both within a consumer project (resolving entry from mfConfig) and in standalone mode (providing the remoteEntry URL directly).
  • Use Case: Quickly check what components a remote Module Federation app exposes and its dependency graph before integrating it into your project.

Quick Start

Get the module information for the 'cart' remote, assuming it's configured in the current project.

Frequently Asked Questions about mf-module-info

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

FAQPage Schema
How do I inspect the exposed modules and shared dependencies of a remote Module Federation app?

You can inspect a remote Module Federation app by parsing its mf-manifest.json to extract exposed modules, remotes, and shared dependencies. This identifies available components and their configurations before integration.

How do I find the remoteEntry URL and publicPath for a Module Federation module?

Finding the remoteEntry URL and publicPath requires fetching the module's metadata. You can resolve these entry points either from a consumer project's mfConfig or by providing the remoteEntry URL directly in standalone mode.

Can I retrieve Module Federation module details without integrating it into a host project?

Yes, you can retrieve Module Federation module details without a host project by using standalone mode. This allows you to provide the remoteEntry URL directly to fetch manifest information and inspect exposed modules independently.

What does the mf-manifest.json file contain for a Webpack Module Federation setup?

The mf-manifest.json file contains the configuration details for a Webpack Module Federation setup, specifically detailing the module's exposes, remotes, and shared dependencies alongside publicPath and remoteEntry URLs.

Do I need Node.js to fetch metadata for a remote Module Federation module?

Yes, you need Node.js installed as it is a required dependency for running the scripts that fetch metadata and parse manifest information for remote Module Federation modules.