What problem does it solve?
This guide helps teams structure SPA routes and ensure parity between desktop and mobile router configurations, preventing navigation drift and blank-screen issues when editing app routes.
Core Features & Use Cases
- Clarifies what belongs in src/routes/ (roots) vs src/features/ (domain logic) and how to separate concerns.
- Enforces desktop router parity by requiring updates to both src/spa/router/desktopRouter.config.tsx and src/spa/router/desktopRouter.config.desktop.tsx in every change.
- Provides a concrete workflow for adding a new SPA route: create thin route files under src/routes and migrate underlying logic into the appropriate domain feature under src/features/.
- Guides route registration and synchronization across the router configuration to prevent drift and navigation issues.
Quick Start
Create a new route segment by adding thin route files under src/routes and migrate related logic into a matching src/features domain, then update both desktopRouter.config.tsx and desktopRouter.config.desktop.tsx to reflect the new path.