React and Angular Integration

In this lesson you will learn react and angular integration in single-spa, why it matters within cross-framework integration, and how to use it correctly with clear, copy-ready examples.

React and Angular Integration Overview

React and Angular Integration 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 react and angular integration focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

import React from 'react';
import ReactDOMClient from 'react-dom/client';
import singleSpaReact from 'single-spa-react';
import Root from './root.component';

const lifecycles = singleSpaReact({
  React,
  ReactDOMClient,
  rootComponent: Root,
});

export const { bootstrap, mount, unmount } = lifecycles;

single-spa-react adapts a React app into single-spa lifecycle functions.

React and Angular Integration Example

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

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

Single-SPA Cheatsheet

Core single-spa APIs related to react and angular integration.

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 React and Angular Integration Works in Single-SPA

React and Angular Integration 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-react adapts a React app into single-spa lifecycle functions.

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 React and Angular Integration

For reliable micro frontends, react and angular integration 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 react and angular integration snippets without understanding what each line does.
Skipping error handling and edge cases when wiring up react and angular integration.
Leaving react and angular integration untested, so regressions slip into production.
Over-engineering react and angular integration before you actually need the extra flexibility.

Key Takeaways

React and Angular Integration is a core part of working effectively with single-spa.
Start small and keep react and angular integration focused on a single responsibility.
Apply consistent patterns so react and angular integration scales across your project.
Test and document react and angular integration to keep it maintainable over time.

Pro Tip

When you get stuck on react and angular integration, reduce it to the smallest reproducible example first — most single-spa issues become obvious once the noise is gone.