ToolingDiagnostics first

Debugging

Start with Axonyx diagnostics before reading generated Rust. The CLI can isolate syntax, route graph, package, state, API, database, and production configuration problems from the app root.

Check source first

cargo ax check
cargo ax check --file app/posts/page.asx

Diagnostics include the source file, line, stable error code, a short problem description, and a corrective hint when one exists.

Inspect the whole app

cargo ax doctor
cargo ax doctor --deny-warnings

Doctor checks package resolution, UI assets, runtime/config state, the route diagnostics, API contracts, Melt output, Aegis setup, and production server readiness.

Inspect generated contracts

cargo ax routes
cargo ax actions --schema
cargo ax state
cargo ax melt --check
cargo ax api --schema

Use these reports when a page exists but receives the wrong data, an action cannot see state, or a route is not where you expect it.

Runtime failures

Development responses may expose actionable diagnostics. Production responses use the nearest `error.asx` or `not-found.asx` boundary and hide internal details from visitors while request logs keep the operational context on the server.

cargo ax run dev