Single-SPA with Module Federation

with Module Federation is an important part of building production-ready single-spa systems. This lesson explains what with module federation means, how it works, and how to apply it with practical examples you can reuse.

with Module Federation Overview

with Module Federation lets you structure single-spa work so it stays readable, testable, and easy to scale. Instead of ad-hoc code, you follow a clear pattern that other developers can recognise immediately.

The key is to keep with module federation focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

import { registerApplication, start } from 'single-spa';

registerApplication({
  name: '@org/app',
  app: () => System.import('@org/app'),
  activeWhen: ['/app'],
});

start();

single-spa orchestrates multiple framework apps on one page through a root config.

with Module Federation Example

registerApplication({
  name: '@org/app',
  app: () => System.import('@org/app'),
  activeWhen: ['/app'],
});
start();

Start from a minimal with Module Federation example and grow it only as needed.
Keep configuration explicit so with Module Federation behaves the same in every environment.
Name things clearly so teammates understand your with Module Federation at a glance.
Add tests around with Module Federation early to lock in expected behaviour.

Single-SPA Cheatsheet

Core single-spa APIs related to with module federation.

API	Example	Purpose
registerApplication	`registerApplication({ name, app, activeWhen })`	Register a micro frontend
activeWhen	`activeWhen: ['/checkout']`	Route ownership
start	`start()`	Begin routing
bootstrap	`export async function bootstrap()`	One-time setup
mount	`export async function mount(props)`	Render the app
unmount	`export async function unmount(props)`	Clean up the app
import map	`systemjs-importmap`	Locate app bundles

How with Module Federation Works in Single-SPA

with Module Federation is part of how single-spa lets multiple applications — even in different frameworks — coexist on one page. A root config registers each app and controls when it is active.

single-spa orchestrates multiple framework apps on one page through a root config.

A root config registers apps and calls start().
Each app exports bootstrap, mount, and unmount lifecycles.
activeWhen decides which routes each app owns.
Import maps resolve each app's bundle at runtime.

Practical Guidance for with Module Federation

For reliable micro frontends, with module federation should isolate failures and keep shared state minimal. Let each team own its app end to end while agreeing on a few shared contracts.

Concern	Recommendation
Isolation	One app's crash should not break others
Shared state	Prefer shared utility modules over globals
Routing	Keep activeWhen rules explicit and non-overlapping
Deployment	Release via import-map updates per app

Common Mistakes

Copying with module federation snippets without understanding what each line does.
Skipping error handling and edge cases when wiring up with module federation.
Leaving with module federation untested, so regressions slip into production.
Over-engineering with module federation before you actually need the extra flexibility.

Key Takeaways

with Module Federation is a core part of working effectively with single-spa.
Start small and keep with module federation focused on a single responsibility.
Apply consistent patterns so with module federation scales across your project.
Test and document with module federation to keep it maintainable over time.

Pro Tip

When you get stuck on with module federation, reduce it to the smallest reproducible example first — most single-spa issues become obvious once the noise is gone.