mf-module-info

To inspect remote Module Federation modules, fetch the module's manifest to retrieve its public path, remote entry URL, type declarations, and lists of exposed, remote, and shared dependencies. This analysis simplifies integration and debugging without digging through configuration files.

You can retrieve metadata including the module's public path, the remote entry URL, and type declaration locations such as @mf-types.zip. The analysis also lists exposed, remote, and shared dependencies defined by the remote application.

Yes, you can analyze a micro-frontend module in standalone mode by providing the explicit remote entry URL directly. Alternatively, it resolves remotes from your project's mfConfig when used within a consumer project.

You can list shared dependencies by analyzing the module's manifest. The Skill parses the remote Module Federation configuration to extract and display all shared, exposed, and remote modules defined by that application.

Yes, the dependency analysis tool supports fetching metadata over both http and https protocols. It retrieves the remote entry URL and manifest data regardless of which protocol the micro-frontend module is served over.

The best way to verify exposed modules is to fetch the remote module's manifest using its entry URL or mfConfig. This lists all exposed modules and entry points directly, preventing manual configuration file searches during integration.