Files describe the journey
The routes folder is the map. The generated route tree turns that map into end-to-end navigation types.
src/routesAbout the starter
Built for a loop: route, load, render, improve.
This project keeps the framework surface visible. There is no UI kit, remote data layer, or hidden generator beyond TanStack Router’s route tree.
Loaders own page data
Each route declares what it needs before rendering, so pending, error, and success states have a natural home.
Route.loaderServer functions cross the boundary
Server-only work remains callable from loaders and components through a typed function contract.
createServerFnPrinciple A
Prefer visible machinery.
Example code should reveal the request path, not conceal it behind premature abstractions.
Principle B
Keep the loop short.
Vite+ owns install, check, test, and build commands so the feedback cycle stays consistent across packages.