Navigated to /docs/cli/develop-and-inspect

Develop and inspect

Run the correct development mode and ask the CLI for route, project, diagnostic, and entity information instead of guessing.

Choose CSR or SSR development

Use the standard dev command for fast client iteration. Add SSR when working on loaders, actions, sessions, server middleware, hydration, or request-time metadata.

BASH
bash# Choose one server; stop it with Ctrl+C before changing modes.
npx tavo dev

# Or test request-time server behavior:
npx tavo dev --ssr

CSR means client-side rendering in the browser. SSR means server-side rendering for the initial request, followed by hydration, which attaches client behavior to the existing HTML. A page working in CSR mode does not verify its server-only data or hydration behavior.

Inspect the project at the right level

  • routes shows URL patterns, source files, layouts, and route parameters.

  • inventory lists pages, components, stores, actions, CSS, exports, and imports.

  • info summarizes framework and project configuration.

  • doctor reports project-shape problems without running a production build.

  • check adds lightweight validation and the local typecheck script when available.

BASH
bashnpx tavo routes
npx tavo inventory --json
npx tavo doctor
npx tavo check

Inspect one entity before changing it

inspect returns focused information for a route, component, store, file, or public API. JSON output includes imports, parse status, and a content hash that automated change plans can use as a stale-write guard.

BASH
bashnpx tavo inspect route /dashboard --json
npx tavo inspect component ProjectCard --json
npx tavo inspect api defineRoutePage --json

Diagnose common development problems

SymptomNext check
tavo cannot be found or npx offers to install itCheck that you are in the application directory, install its dependencies, and confirm @tavojs/cli is a development dependency. Do not accept an unrelated package as a substitute for the local binary.
A new page returns 404Run npx tavo routes and check the URL, default export, and configured pagesDir. File names and route groups determine the URL; a source path is not the browser URL.
Server data works in one mode but fails in anotherRun npx tavo dev --ssr for server loaders, actions, and sessions. Test both a direct request and client navigation, and inspect the terminal as well as browser diagnostics.
Preview still shows old contentStop preview, run npx tavo build again, and restart preview. Preview serves the last build; it does not watch source files.
A diagnostic needs more investigationCapture the failing command, its output, npx tavo --version, and the relevant route or file. Reduce the issue to a small reproducible example before reporting it.