module-federation-expose

Manage Module Federation exposes in erxes frontend plugin configuration files.

4.1k|1.3k|Updated Nov 11, 2016

Search Tags:#frontend #plugin #monorepo #expose #module-federation #shared-dependencies #erxes

Ready to run

npx skills add https://github.com/erxes/erxes --skill module-federation-expose

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: module-federation-expose
Source: https://github.com/erxes/erxes/tree/main/.agents/skills/module-federation-expose
Command: npx skills add https://github.com/erxes/erxes --skill module-federation-expose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the complexity and risk of managing Module Federation exposes in erxes plugins, preventing build failures and integration issues by enforcing architectural best practices.

Core Features & Use Cases

Guided Configuration: Assists in adding/modifying exposes in module-federation.config.ts with validation
Boundary Enforcement: Ensures entry points remain stable and minimal across plugin boundaries
Dependency Management: Maintains consistency with shared dependencies and host references
Use Case: When developing a new feature requiring cross-plugin access (e.g., exposing a settings page from a plugin to the host application)

Quick Start

Help me add a new route module expose for the 'marketing-plugin' plugin.

Frequently Asked Questions about module-federation-expose

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

FAQPage Schema

How do I expose a route module using Module Federation in an Nx monorepo?▼

To expose a route module using Module Federation, you update the module-federation.config.ts file to define the entry point. This ensures stable, minimal plugin boundaries and coordinates shared dependencies for a consistent build.

What is the safest way to manage cross-plugin component exposures in a frontend monorepo?▼

Managing cross-plugin exposures safely requires enforcing architectural boundaries by keeping entry points minimal and stable. Validating configurations against host references and shared dependencies prevents integration issues and build failures.

How do I add a new widget expose to a frontend plugin without breaking shared dependencies?▼

When adding a widget expose, you must maintain consistency with existing shared dependencies and host references. Validating the new entry point in the configuration file ensures the plugin boundary remains stable and prevents build failures.

Why does modifying Module Federation exposes cause build failures in frontend plugins?▼

Build failures occur when exposes are added or modified without coordinating with host references and shared dependencies. Enforcing minimal entry points and validating the configuration helps maintain a consistent build across plugin boundaries.

Can I use this approach to expose a settings page from a plugin to the host application?▼

Yes, you can expose a settings page by adding the route module to your configuration. This guided process validates the entry point to ensure safe cross-plugin access while maintaining stable host application integration.