Routes and server functions

Select an app#

Open View → Tool Windows → TanStack, then inspect the Project summary. In a workspace, select the application whose routes you want to inspect. Verify its routes directory and generated route tree before creating files.

Explore file routes#

Use Route Tree to navigate route declarations and see badges for loaders, components, pending/error/not-found states, and server routes. Route Health compares source routes with the generated tree and reports missing, mismatched, or deleted references.

Use the project generator when the tree is stale. Tool-window actions can create child routes and route files; review their location and naming before accepting. Avoid manually changing generated output as a permanent fix.

Find callers#

Inspect Route Usages for links, navigation, redirects, route APIs, and preload calls. Follow a usage back to source and use completion when changing a route reference. Inspections can identify broken links or missing required route parameters.

Inspect server boundaries#

The Server panel indexes createServerFn, route handlers, and server-related declarations. Review client/server misuse warnings alongside the actual framework build. These checks assist code review but cannot prove that all runtime data or authentication paths are correct.