I somehow missed that feature in the docs completely! I still like the HOC approach because it keeps the routes nested - making things like breadcrumbs easier to reason about.

Great picture! The Kingfisher at my local is just too elusive.

Tanrouter renders child routes via Outlets in the parent. You can an underscore suffix to unnest them, but this changed our directory structure too much.

The solution was pretty simple. A HOC that checks for a child route. If found it renders an Outlet. Otherwise it renders the current route.

It was a custom file based router that used react router 5 under the hood.

We migrated to tanstack router for a few months before moving to start (work is complete but not merged to main)

The hardest part for us was how we treated nested routes. We nested logically but not visibly.

Would feedback on #Start count?

I've migrated two apps now with very positive results.

1) 25 route Next app - This went very smoothly - no issues.

2) 150+ route Vite SPA. Trickier, since we have uses of `window` sprinkled throughout.

Only issue is with HMR in both, but I haven't investigate.