Application Parcels

Application Parcels is an important part of building production-ready single-spa systems. This lesson explains what application parcels means, how it works, and how to apply it with practical examples you can reuse.

Application Parcels Overview

Application Parcels 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 application parcels focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

import Parcel from 'single-spa-react/parcel';

<Parcel
  config={() => System.import('@org/product-card')}
  wrapWith="div"
  productId={id}
/>

Parcels let one framework render a component owned by another, independent of routing.

Application Parcels Example

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

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

Single-SPA Cheatsheet

Core single-spa APIs related to application parcels.

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 Application Parcels Works in Single-SPA

Application Parcels 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.

Parcels let one framework render a component owned by another, independent of routing.

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 Application Parcels

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

Key Takeaways

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

Pro Tip

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