Micro Frontend State Management

Micro Frontend State Management Overview

At its core, micro frontend state management is about doing one thing well inside your single-spa project. Once you understand the pattern, you can apply it consistently across features and teams.

Good micro frontend state management pays off across the whole codebase: fewer surprises, easier testing, and smoother onboarding. The snippet below is a solid starting point.

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.

Micro Frontend State Management Example

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

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

Single-SPA Cheatsheet

Core single-spa APIs related to micro frontend state management.

How Micro Frontend State Management Works in Single-SPA

Micro Frontend State Management 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 Micro Frontend State Management

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

Common Mistakes

• Skipping error handling and edge cases when wiring up micro frontend state management.
• Leaving micro frontend state management untested, so regressions slip into production.
• Over-engineering micro frontend state management before you actually need the extra flexibility.
• Ignoring documentation, which makes micro frontend state management hard for the next developer to change.

Key Takeaways

• Micro Frontend State Management is a core part of working effectively with single-spa.
• Start small and keep micro frontend state management focused on a single responsibility.
• Apply consistent patterns so micro frontend state management scales across your project.
• Test and document micro frontend state management to keep it maintainable over time.