mf-module-info

Step 2 — consumer mode (no URL provided): Call the mf-context Skill (passing [project-root]) to collect MFContext, then run:

Step 2 — standalone mode (URL provided): Run with an empty context and the explicit URL:

| publicPath | Base URL of the remote | | remoteEntry | Full URL to remoteEntry.js | | typesZip | URL to @mf-types.zip | | typesApi | URL to @mf-types.api (shown only if present) | | hasSsr | Whether SSR build artifacts were detected | | exposes | Modules this remote exposes | | remotes | Remotes this module depends on |

Fetch metadata and manifest info for a remote Module Federation module — publicPath, remoteEntry, type file URLs, and the module's remotes/exposes/shared from its mf-manifest.json. Two modes: (1) inside a consumer project, pass only the remote name and the entry URL is resolved from mfConfig.remotes; (2) outside a consumer project, pass the remote name plus its remoteEntry URL directly. To inspect the current project's own config, use mf-context instead. Source: module-federation/core.