Micro-frontend capabilities
Every capability below is loaded through sample-remote-app and composed into this shell. Open any card to run it in place, then record a host-side interaction to contrast host and remote attribution.
Composition & Rendering
Remote capabilities
A remote-exposed Server Component renders inside the shell and links onward to every other capability.
Open →Composition & RenderingShell-embed header (App Router)
The remote reads the x-shell-embed header to detect composition without owning the browser origin.
Open →Navigation & Routing
Remote → shell navigation
A next/link click inside the remote becomes a shell URL, so browser history and deep links stay host-owned.
Open →Navigation & RoutingLink navigation matrix
Soft-nav, cross-origin, and server-redirect links each resolve correctly — no SecurityError.
Open →Navigation & RoutingInternal server redirect
A server redirect() inside the remote is followed by the shell proxy and the shell URL updates.
Open →Navigation & RoutingExternal server redirect
A redirect() to an outside origin leaves the shell via the proxy external-redirect header.
Open →Data & GraphQL
API-route data fetch
A remote Server Component fetches its own API route server-side and drives the shell breadcrumb and title.
Open →Data & GraphQLGraphQL RSC + metadata gate
A remote resolves a GraphQL query in-process; its metadata endpoint can gate access before content renders.
Open →