Getting Started — Overview

Quick navigation to every "Getting Started" page across the Native Federation sections — pick the one that matches what you're building.

Native Federation consists of two components — a builder for the remotes (micro frontends), and a runtime for the shell/host.

The builder itself splits in two: a Core that does the heavy lifting, and a bundler-specific Adapter (Angular, esbuild, …) that wires the Core into your build pipeline. The runtime comes in two flavours: the classic Runtime, or the newer Orchestrator with semver-aware version resolution and cross-reload caching.

Each piece has its own getting-started page — pick the one that matches what you're building.

Build a remote

• Core — Getting Started — install @softarc/native-federation and wire the core builder into a custom build script with a bundler adapter. v4.
• esbuild Adapter — Getting Started — install the esbuild adapter and build your first React remote end-to-end. v4.
• Angular Adapter — Getting Started — scaffold a host and a remote with ng add in minutes. v4.

Load remotes on a host at runtime

• Orchestrator — Getting Started — the drop-in quickstart bundle, the event registry, and writing your own initFederation script. v3 & v4.
• Classic Runtime — Getting Started — install @softarc/native-federation-runtime, add es-module-shims, split your bootstrap, and load your first remote module. v3 & v4.

New to Native Federation?

If you've landed here without context, start with the conceptual pages first:

• Architecture Overview — how Core, Adapters, Runtime and Orchestrator fit together.
• The Mental Model — hosts, remotes, shared dependencies, and version handling.
• Terminology — the vocabulary used across the docs.
• v3 vs v4 — when to use which, and what changed.