Hash Routing

Hash Routing sits at the heart of routing in single-spa. This guide walks through the concept step by step, with examples, a cheatsheet, and common mistakes to avoid.

Hash Routing Overview

Hash Routing 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 hash routing focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

registerApplication({
  name: '@org/checkout',
  app: () => System.import('@org/checkout'),
  activeWhen: (location) => location.pathname.startsWith('/checkout'),
});

activeWhen decides which route ranges a micro frontend owns.

Hash Routing Example

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

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

Single-SPA Cheatsheet

Core single-spa APIs related to hash routing.

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 Hash Routing Works in Single-SPA

Hash Routing 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.

activeWhen decides which route ranges a micro frontend owns.

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 Hash Routing

For reliable micro frontends, hash routing 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

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

Key Takeaways

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

Pro Tip

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