This example demonstrates a runtime plugin implementation for Module Federation that provides dynamic control over shared module versions. It allows you to deterministically manage and modify shared module versions across federated applications using a control panel interface and localStorage persistence.

• Runtime plugin for dynamic version control of shared modules
• Control panel UI for managing shared module versions
• Persistent version settings using localStorage (formDataVMSC key)
• Support for upgrading/downgrading shared module versions
• E2E tests to verify version control functionality

A runtime plugin that implements version control for Module Federation. Key features:

• Implements the FederationRuntimePlugin interface
• Uses localStorage to persist version preferences
• Handles version resolution and module sharing between applications
• Manages share scope mapping and instance tracking

Comprehensive E2E tests that verify:

• Initial shared module versions
• Version override functionality through localStorage
• UI updates reflecting version changes
• Button component rendering with correct version information

Run pnpm run start. This will build and serve both app1 and app2 on ports 3001 and 3002 respectively.

• localhost:3001 - Host application with control panel
• localhost:3002 - Remote application

To run tests in interactive mode:

To run tests in headless mode:

yarn e2e:ci

The control panel allows you to:

• View current versions of shared modules (react, react-dom, lodash)
• Override versions for specific applications
• Save settings to localStorage
• Clear settings and reload to default versions

The runtime plugin (control-share.ts) handles:

• Version resolution based on localStorage settings
• Share scope management
• Instance tracking and updates
• Cross-application module sharing rules