Titan Logs

Overview

Titan provides structured, readable terminal logs that reflect what is happening inside the native Rust server at runtime.
These logs are designed to help you understand routing, action execution, performance, and request flow—without noise.

Titan logs are emitted directly by the Rust server and the JavaScript runtime layer.

Server startup logs

When you run Titan in development mode, the server prints startup information to the terminal.

Titan server running at: http://localhost:5000

This confirms that:

The Rust server compiled successfully
Routes and actions were loaded
The HTTP server is listening and ready

Build and bundling logs

During development, Titan automatically bundles actions and regenerates metadata when files change.

[Titan] Bundling actions...
[Titan] Bundling app/actions/hii.js → server/actions/hii.jsbundle
[Titan] Bundling finished.
Titan: routes.json + action_map.json written

These logs indicate:

JavaScript actions are bundled into .jsbundle files
Routing metadata is regenerated
The Rust server is aware of the latest application state

Automatic server restarts

When routes or actions change, Titan restarts the Rust server automatically.

[Titan] Restarting Rust server...
[Titan] Rust server exited: 1
Running target/debug/server.exe

This ensures:

No manual restarts are required
The running server always reflects current code
Development feedback is fast and deterministic

Request execution logs

For every incoming request, Titan logs a concise execution summary.

[Titan] GET /hii → hii (dynamic) in 7.70ms

This log shows:

HTTP method (GET)
Request path (/hii)
Action name (hii)
Route type (dynamic)
Execution time (7.70ms)

This makes it easy to track performance and behavior per request.

Action-level logs (`t.log`)

Inside actions, you can emit logs using t.log().

t.log(req)

These logs appear in the terminal as structured output:

[Titan] log(hii): {
  body: null,
  method: "GET",
  path: "/hii",
  params: {},
  query: {}
}

This is useful for:

Debugging request data
Inspecting parameters and queries
Tracing action execution

Unlike console.log, t.log is routed through Titan’s logging system and remains consistent across environments.

Error logs

When an action throws an error or fails during execution, Titan logs a structured error summary in the terminal.
This allows you to quickly identify what failed, where it failed, and how long the request ran before failing.

[Titan] GET / → error in 13.51ms
Action: hii
ReferenceError: var is not defined

What this log means

GET / The incoming HTTP request and path.
→ error Indicates the request failed during execution.
13.51ms Total time spent before the error occurred.
Action: hii The action responsible for handling the request.
ReferenceError: var is not defined The JavaScript runtime error thrown inside the action.